Tap any paragraph to write a margin note. Your notes collect in the Desk below the text and file under cases with @. The side-by-side margin rail opens on a larger screen.

§
Marginalia
Code · REGISTER · 2007-01-23 · Food and Drug Administration, HHS · Proposed Rules

Proposed Rules. Proposed rule

63,455 words·~288 min read·/register/2007/01/23/07-257

A research copy — for the controlling text, always check the official state or federal source. Not legal advice.

BILLING CODE 3510-22-S 72 14 Tuesday, January 23, 2007 Proposed Rules DEPARTMENT OF HEALTH AND HUMAN SERVICES Food and Drug Administration 21 CFR Part 101 [Docket No. 2005N-0279] RIN 0910-ZA26 Food Labeling; Gluten-Free Labeling of Foods AGENCY: Food and Drug Administration, HHS. ACTION: Proposed rule. SUMMARY: The Food and Drug Administration
(FDA)is proposing to define the term “gluten-free” for voluntary use in the labeling of foods, to mean that the food does not contain any of the following: An ingredient that is any species of the grains wheat, rye, barley, or a crossbred hybrid of these grains (all noted grains are collectively referred to as “prohibited grains”); an ingredient that is derived from a prohibited grain and that has not been processed to remove gluten (e.g., wheat flour); an ingredient that is derived from a prohibited grain and that has been processed to remove gluten (e.g., wheat starch), if the use of that ingredient results in the presence of 20 parts per million
(ppm)or more gluten in the food; or 20 ppm or more gluten. A food that bears the claim “gluten-free” or similar claim in its labeling and fails to meet the conditions specified in the proposed definition of “gluten-free” would be deemed misbranded. FDA also is proposing to deem misbranded a food bearing a gluten-free claim in its labeling if the food is inherently free of gluten and if the claim does not refer to all foods of that same type (e.g., “milk, a gluten-free food” or “all milk is gluten-free”). In addition, a food made from oats that bears a gluten-free claim in its labeling would be deemed misbranded if the claim suggests that all such foods are gluten-free or if 20 ppm or more gluten is present in the food. Establishing a definition of the term “gluten-free” and uniform conditions for its use in the labeling of foods is needed to ensure that individuals with celiac disease are not misled and are provided with truthful and accurate information with respect to foods so labeled. This proposed action is in response to the Food Allergen Labeling and Consumer Protection Act of 2004 (FALCPA). DATES: Submit written or electronic comments by April 23, 2007. ADDRESSES: You may submit comments, identified by Docket No. 2005N-0279, by any of the following methods: *Electronic Submissions* Submit electronic comments in the following ways: • Federal eRulemaking Portal: *http://www.regulations.gov* . Follow the instructions for submitting comments. • Agency Web site: *http://www.fda.gov/dockets/ecomments* . Follow the instructions for submitting comments on the agency Web site. *Written Submissions* Submit written submissions in the following ways: • FAX: 301-827-6870. • Mail/Hand delivery/Courier [For paper, disk, or CD-ROM submissions]: Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852. To ensure more timely processing of comments, FDA is no longer accepting comments submitted to the agency by e-mail. FDA encourages you to continue to submit electronic comments by using the Federal eRulemaking Portal or the agency Web site, as described in the *Electronic Submissions* portion of this paragraph. *Instructions* : All submissions received must include the agency name and Docket No(s). and Regulatory Information Number
(RIN)(if a RIN number has been assigned) for this rulemaking. All comments received may be posted without change to *http://www.fda.gov/ohrms/dockets/default.htm* , including any personal information provided. For detailed instructions on submitting comments and additional information on the rulemaking process, see the “Comments” heading of the SUPPLEMENTARY INFORMATION section of this document. *Docket* : For access to the docket to read background documents or comments received, go to *http://www.fda.gov/ohrms/dockets/default.htm* and insert the docket number(s), found in brackets in the heading of this document, into the “Search” box and follow the prompts and/or go to the Division of Dockets Management, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852. FOR FURTHER INFORMATION CONTACT: Rhonda R. Kane, Center for Food Safety and Applied Nutrition (HFS-820), Food and Drug Administration, 5100 Paint Branch Pkwy., College Park, MD, 301-436-2371, FAX: 301-436-2636, e-mail: *rhonda.kane@fda.hhs.gov* . SUPPLEMENTARY INFORMATION: Table of Contents I. Background A. Celiac Disease B. Prevalence of Celiac Disease in the United States C. Gluten and the Grains of Concern for Individuals with Celiac Disease 1. Meaning of the Term “Gluten” 2. Grains of Concern to Individuals with Celiac Disease 3. Uncertainty About Including Oats in the Diet of Individuals with Celiac Disease D. FDA's Prior Statements on Gluten-Free Food Labeling E. Food Allergen Labeling and Consumer Protection Act of 2004 and Related Activities 1. Food Allergen Labeling and Consumer Protection Act of 2004 2. FDA's Threshold Working Group and Its Report on Approaches to Establish Thresholds 3. Food Advisory Committee Meeting of July 13-15, 2005 4. Gluten-Free Food Labeling Public Meeting of August 19, 2005 II. Proposed Rule A. Legal Basis B. Definitions and Criteria for the Use of the Term Gluten-Free in Food Labeling 1. Definitions of the Terms “Prohibited Grains” and “Gluten” 2. Definition of the Term “Gluten-Free” 3. Use of the Term Gluten-Free in the Labeling of Foods That Inherently Do Not Contain Gluten 4. Use of the Analytical Methods-Based Approach in this Proposed Rule to Set a Threshold Level of 20 ppm to Define the Term Gluten-Free C. Compliance and Enforcement of an FDA Gluten-Free Food Labeling Claim III. Preliminary Regulatory Impact Analysis A. Need for This Regulation B. Proposed Regulatory Options C. Impacts of the Proposed Regulatory Options 1. Option One: Take No Action 2. Option Two: Take the Proposed Action—Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing the Prohibited Grains or Ingredients That Have Been Derived From Those Grains and Have Not Been Processed to Remove the Gluten; Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing Ingredients Derived From the Prohibited Grains That Have Been Processed to Remove the Gluten, If the Level of Gluten Is 20 ppm or Greater; Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing 20 ppm or More Gluten, Regardless of How the Gluten Got Into the Food; and Restrict Wording of Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten a. Overview b. Costs c. Benefits d. Summary 3. Option Three: Take the Proposed Action, Except Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing Ingredients Derived From the Prohibited Grains That Have Been Processed to Remove The Gluten, If the Level of Gluten Is Some Specified Level Other Than 20 ppm, and Do Not Permit Firms to Make Gluten-Free Claims on Foods If the Level Of Gluten Is Some Specified Level Other Than 20 ppm, Regardless of How the Gluten Got Into the Food a. Overview b. Costs c. Benefits d. Summary 4. Option Four: Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing 20 ppm or More Gluten, Regardless of the Ingredients They Use to Make Them, and Restrict the Wording of Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten 5. Option Five: Take the Proposed Action, Except Delete Wording Requirements for Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten 6. Option Six: Take the Proposed Action, but Also Define the Food Labeling Claim “Low Gluten” 7. Option Seven: Take Proposed Action, Except Include Oats in the List of Grains That We Propose to Prohibit in Foods That Firms Label as Gluten-Free IV. Regulatory Flexibility Analysis A. Proposed Regulatory Options B. Impacts of the Proposed Regulatory Options on Small Entities 1. Option One: Take No Action 2. Option Two: Take the Proposed Action—Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing the Prohibited Grains or Ingredients That Have Been Derived From Those Grains and Have Not Been Processed to Remove the Gluten; Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing Ingredients Derived From the Prohibited Grains That Have Been Processed to Remove the Gluten, If the Level of Gluten Is 20 ppm or Greater; Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing 20 ppm or More Gluten, Regardless of How the Gluten Got Into the Food; and Restrict Wording of Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten 3. Option Three: Take the Proposed Action, Except Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing Ingredients Derived From the Prohibited Grains That Have Been Processed to Remove the Gluten, If the Level of Gluten Is Some Specified Level Other Than 20 ppm, and Do Not Permit Firms to Make Gluten-Free Claims on Foods If the Level of Gluten Is Some Specified Level Other Than 20 ppm, Regardless of How the Gluten Got Into the Food 4. Option Four: Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing 20 ppm or More Gluten, Regardless of the Ingredients They Use to Make Them, and Restrict the Wording of Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten 5. Option Five: Take the Proposed Action, Except Delete Wording Requirements for Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten 6. Option Six: Take the Proposed Action, but Also Define the Food Labeling Claim “Low Gluten” 7. Option Seven: Take Proposed Action, but Include Oats in the List of Grains That We Propose to Prohibit in Foods That Firms Label as Gluten-Free V. Unfunded Mandates VI. Executive Order 13132: Federalism VII. Environmental Impact Analysis VIII. Paperwork Reduction Act of 1995 IX. Comments X. References I. Background A. Celiac Disease Celiac disease (also known as celiac sprue and gluten-sensitive enteropathy) is a chronic inflammatory disorder of the small intestine in genetically susceptible individuals triggered by ingesting certain storage proteins, commonly referred to as “gluten,” that naturally occur in some cereal grains (Refs. 1 through 3). In such individuals, the consumption of gluten stimulates the production of antibodies and inflammatory cells, resulting in an abnormal immune response, which damages the tiny, fingerlike protrusions called “villi” that line the small intestine and function to absorb nutrients from food (Ref. 4). Over time, continued dietary exposure to gluten can destroy the intestinal villi of individuals who have celiac disease, leading to a lack of absorption of nutrients and wide variety of other serious health problems (Ref. 4). The symptoms and clinical manifestations of celiac disease are highly variable among affected individuals and differ in severity. The reasons for this variability are unknown, but may depend upon the age and immunological status of the individual, the amount, duration or timing of the exposure to gluten, and the specific area and extent of the gastrointestinal tract involved by disease (Ref. 5). Symptoms of celiac disease may be:
(1)“Classical,” affecting the digestive tract (e.g., abdominal bloating; cramping and pain; chronic diarrhea; vomiting; constipation) and resulting in gastrointestinal malabsorption; or
(2)“atypical,” affecting mainly other parts of the body (e.g., fatigue; irritability; behavior changes; bone or joint pain; tingling numbness in the legs; ulcers in the mouth; tooth discoloration or loss of enamel; itchy skin rash with blisters called dermatitis herpetiformis) (Refs. 1, 4, 6, and 7). A large portion of the subpopulation that has celiac disease may not experience any symptoms at all and are classified as having “silent” or “latent” forms of celiac disease (Refs. 1 and 8). Persons who have the silent form of celiac disease have most of the diagnostic features commonly seen in individuals with classical or atypical celiac disease, such as specific serum antibodies and evidence of damaged intestinal villi. Those who have the latent form of celiac disease have specific serum antibodies, but no evidence of damaged intestinal villi (Ref. 1). In addition to the aforementioned clinical symptoms and ailments, celiac disease is associated with a number of significant health problems and disorders, including but not limited to: Iron-deficiency anemia, vitamin deficiencies, protein-calorie malnutrition, weight loss, short stature, growth retardation in children, delayed puberty, infertility, miscarriage, and osteoporosis (Refs. 1, 6, 9, and 10). Individuals with unmanaged celiac disease are at an increased risk of developing other serious medical conditions, such as Type I diabetes mellitus, intestinal cancers, and both intestinal and extraintestinal non-Hodgkin's lymphomas (Refs. 7 and 11 through 13). Celiac disease has no cure, but individuals who have this disease are advised to avoid all sources of gluten in their diet (Refs. 1 and 6). Over time, strictly avoiding consumption of all sources of gluten can resolve the symptoms, mitigate and possibly reverse the damage, and reduce the associated health risks of celiac disease (Ref. 14). For some individuals with celiac disease, failure to avoid consumption of gluten can lead to severe and sometimes life-threatening complications that can affect multiple organs of the body (Refs. 5, 6, and 15). B. Prevalence of Celiac Disease in the United States Precise prevalence data for celiac disease are not available. The overall prevalence of celiac disease in the U.S. is currently estimated to range from about 0.4 percent to about 1 percent of the general population, or approximately 1.5 to 3 million Americans (Refs. 1 and 16). However, the number of Americans with physician-diagnosed celiac disease is estimated at between 40,000 (Ref. 17) and 60,000 (Ref. 18). This discrepancy between estimated prevalence and diagnosed cases has been linked primarily to the fact that celiac disease can be silent or latent. Some researchers have suggested that the true prevalence is underreported (Ref. 8). Silent and latent forms of celiac disease may go undetected in individuals for years before they develop symptoms causing them to seek medical attention (Ref. 13). In addition, celiac disease is often mistaken for other gastrointestinal malabsorption disorders that have similar diarrheal symptoms (e.g., irritable bowel syndrome), which further delays its diagnosis (Ref. 19). Only recently has the medical community become more aware of the need to screen for celiac disease when patients experience health problems that may be associated with the disease or when patients have family members, especially first- and second-degree relatives, who have celiac disease (Ref. 1). C. Gluten and the Grains of Concern for Individuals with Celiac Disease 1. Meaning of the Term “Gluten” There is no single definition of the term “gluten.” Technically, the term “gluten” refers to a specific complex of proteins that forms when wheat flour is mixed with a liquid and physically manipulated, such as in the kneading of a bread (Ref. 20). This complex of proteins is composed of both “gliadins” and “glutenins,” which are found in approximately equal proportions in most wheat varieties (Refs. 21 through 23). The gliadins belong to a category of proteins called “prolamins” and the glutenins belong to a category of proteins called “glutelins” (Refs. 20 and 24). Although, strictly speaking, “gluten” pertains only to wheat proteins, this term is frequently used to refer to the combination of prolamin and glutelin proteins naturally occurring in other grains, including those that have not been demonstrated to cause harmful effects in individuals with celiac disease (e.g., “corn gluten” and “rice gluten”) (Ref. 25). However, in discussions of celiac disease in the medical literature, the term “gluten” is used to refer to either gluten in wheat or collectively to the proteins (e.g., prolamins and glutelins) in just those grains that have been demonstrated to cause harmful health effects in individuals who have celiac disease (Refs. 3 and 25). 2. Grains of Concern to Individuals With Celiac Disease The grains that are reported to contain gluten that can cause harmful health effects in individuals with celiac disease and should be avoided by them are as follows: Wheat (including durum wheat, spelt wheat, and kamut), rye, barley, and crossbred hybrids of these grains (e.g., triticale, which is a cross between wheat and rye), and possibly oats (Refs. 26 through 30). Rye, barley, and triticale are taxonomically very closely related to wheat and contain peptides structurally similar to those found in wheat (Refs. 30 and 31). Although oats are not as closely related to wheat (Ref. 30), they are reported to contain some peptides similar to those found in wheat, which may help to explain why some individuals with celiac disease are sensitive to oats (Ref. 32). In contrast, the cereal grains believed to be well tolerated by individuals with celiac disease and which are not taxonomically as closely related to wheat and are not reported to contain similar peptides to those found in wheat include: Amaranth, buckwheat, corn (maize), Indian ricegrass, Job's tears, millet, quinoa, ragi, rice, sorghum, teff (tef), and wild rice (Refs. 26, 27, 29 through 31, 33, and 34). There is evidence that both the prolamins (i.e., gliadins) and glutelins (i.e., glutenins) in wheat adversely affect individuals with celiac disease (Refs. 2, 27, and 35 through 37). Wheat gliadin subtypes alpha, beta, gamma, and omega have been shown to cause damage to the intestinal tract of individuals with celiac disease (Refs. 38, 39, and 40, p. 41). Moreover, it is also believed that the prolamins in rye (i.e., secalins) and the prolamins in barley (i.e., hordeums) are responsible for causing adverse health effects in individuals with celiac disease (Refs. 13, 23, 28, 41, and 42). Oats also have prolamins (i.e., avenins) that have some amino acid sequences similar to those occurring in wheat and are believed to be harmful to a small subset of individuals with celiac disease (Ref. 32). Although the prolamins of the aforementioned grains and the wheat glutelins are recognized to cause adverse health effects in individuals with celiac disease, all cereal grains contain other types of proteins, including albumins and globulins, which are not currently associated with celiac disease (Refs. 20 and 21). There is still much unknown about all the specific proteins in the different grains that can affect individuals with celiac disease (Ref. 43). 3. Uncertainty About Including Oats in the Diet of Individuals With Celiac Disease Currently, there is no general agreement among experts about the extent to which oats present a hazard for individuals with celiac disease. Whether oats should or should not be consumed by individuals with celiac disease has been the subject of controversy for more than 50 years (Ref. 44). There are inconclusive and conflicting results from research on the effects of oat consumption on individuals with celiac disease. Some of this research, in particular early research, suggests that oat consumption is harmful to individuals with celiac disease (Refs. 26 and 28). More recent studies found that 1 of 19 study participants (Ref. 45) and 4 of 9 participants (Ref. 32) could not tolerate an average of about 50 grams dry weight of oats. The oats used in both studies were tested to ensure that they did not contain gluten proteins from wheat, rye, or barley. However, multiple studies in the last 10 years have shown that the ingestion of oats in the diet of individuals who have celiac disease, in both children and adults, does not necessarily lead to increased intestinal or skin symptoms or to altered intestinal pathology, and appears to be preferred to a diet without oats (Refs. 46 through 51). The average amount of oats consumed by participants in each of these studies differed, ranging from about 15 grams to 60 grams dry weight per day. A long-term study that lasted 5 years concluded that individuals with celiac disease prefer and can tolerate without harmful effects a daily average consumption of 34 grams dry weight of oats (Ref. 49). Although the total number of individuals with celiac disease who are sensitive to oats is unknown, the findings of many of the contemporary studies suggest that the proportion of individuals with celiac disease who cannot tolerate oats in daily amounts of about 50 or less grams dry weight is probably very low. One celiac expert suggests that the size of this subpopulation is likely to be less than one percent of individuals with celiac disease (Ref. 52). Despite the evidence that the consumption of oats does not present a risk for most individuals with celiac disease, a major obstacle impeding general acceptance of oats in the diet of individuals with celiac disease is the concern about the commingling 1 of oats with wheat, rye or barley that can occur during grain production, transport, storage, or processing (Refs. 44 and 53). Due to this concern, Farrell and Kelly (Ref. 7) advise individuals with newly diagnosed celiac disease not to consume oats until their disease is in remission (e.g., intestinal tract has healed). Some celiac disease treatment or research centers in the United States report that they do not support the inclusion of oats in the diet of individuals with celiac disease, whereas other centers do, stating that oats can enhance the nutrient density and fiber content of a diet that avoids all sources of gluten and possibly improve compliance with this very restrictive diet (Refs. 54 through 56). 1 The cited references use the term “contamination,” but other references use the term “commingling.” For purposes of this proposed rule, FDA has opted to use the term “commingling,” and considers that term to mean “the process of mixing.” Thompson (Ref. 57) conducted a small, non-randomized mail survey using a questionnaire about the acceptability of several foods in diets that do not contain gluten. Thirty seven questionnaires, completed by celiac disease organizations (United States and foreign), physicians, and dietitians/nutritionists, were submitted in response to the survey. Only five (i.e., 1 foreign celiac association and 4 physicians) of the 33 respondents who answered the question about oats considered oats to be an acceptable food, and none of the four U.S. celiac disease associations that responded to the survey considered oats to be an acceptable food for individuals with celiac disease. The reasons given by respondents for their lack of acceptance of oats included concerns about the possibility that oats may cause adverse health effects in individuals with celiac disease either directly or due to the presence of gluten from another grain (e.g., wheat, rye, or barley), and about the insufficiency of long-term research that identifies the amount of oats that can be tolerated by individuals with celiac disease. According to more recent position statements of 3 of the 4 major celiac associations in the United States that responded to the earlier survey conducted by Thompson (Ref. 57), one of these associations continues to take the position that oats are not an acceptable food for individuals with celiac disease; but, the other two of these associations are not opposed to the inclusion of oats in the diets of individuals with celiac disease, provided that the oats do not contain gluten from other grains and that the daily amount of oats consumed is limited to 1 cup cooked (Ref. 56). Both of the latter associations state that oats can add soluble fiber and nutrients to a diet that avoids all sources of gluten; but, direct individuals with celiac disease to consult with their health care providers before introducing oats into their diet. Also, both of these associations recommend that individuals with celiac disease who consume oats should have their levels of antibodies specific to celiac disease monitored periodically. The recent *National Institutes of Health Consensus Conference Statement on Celiac Disease* (Ref. 1) does not identify oats as being one of the grains that individuals with celiac disease should avoid. Instead, this statement indicates that it appears that most individuals with celiac disease can include oats in their diet without harmful health effects, but that it may not be practical to do so because oats may contain gluten from other grains due to commingling during their processing. Similarly, the 2006 edition of the American Dietetic Association
(ADA)*Nutrition Care Manual (ADA Manual)* recommends that individuals with celiac disease avoid wheat (including wheat in all of its varieties, such as spelt, and in all of its forms, such as wheat starch), rye, barley and their crossbred hybrid varieties (e.g., triticale), but does not advise individuals with celiac disease to presumptively exclude oats from their diet (Ref 58). Instead, the *ADA Manual* states: “* * *Findings from *in vivo* research on the safety of oats suggest that most persons with celiac disease can safely consume moderate amounts of uncontaminated oats without adversely affecting the intestinal mucosa * * *.” (Ref. 59). However, the *ADA Manual* acknowledges that “* * *limited evidence suggests that in some persons with celiac disease, the consumption of uncontaminated oats may result in mucosal inflammation* * *.” Further, the *ADA Manual* advises that individuals with celiac disease consult with their physicians and dietitians before deciding to consume oats and that any daily intake should be limited to about 50 grams of dry oats that ideally have been tested to ensure that they do not contain gluten from wheat, rye, or barley. The *ADA Manual* also reports that some oat millers have established comprehensive clean-out procedures and control programs to address the problem of commingling of oats with wheat, rye, and barley. In addition, in a letter submitted in response to FDA's 2005 public meeting on gluten-free (see section I.E.4 of this document for details about this meeting), ADA expressed support for FDA establishing a definition of gluten-free for oats that is tied to testing that ensures that those oats do not contain gluten from other grains, so that those oats could bear a gluten-free labeling claim (Ref. 60). The commingling of oats with wheat, rye, barley or their crossbred hybrids or with the grains generally considered to be acceptable for individuals with celiac disease (e.g., corn and rice) can occur at any step in the farm-to-table continuum. This is due to the common practices of growing crops in rotation and in close proximity to one another as well as using the same equipment and storage bins to harvest and hold different grains (Ref. 53). Accordingly, the official U.S. standard for a given grain typically allows for the presence of a small percentage of other grains (Ref. 61). It is believed that most oat products commercially available in the United States contain some gluten from wheat, rye, or barley as a result of commingling during the oats' growth, harvesting, transport, storage, or processing (Refs. 43, 44, 53, 62, and 63). In 2004, Thompson reported that in a recent study 4 samples of each of 3 brands of oat products marketed in the United States were analyzed in duplicate for gluten from wheat, rye, and barley using an enzyme-linked immunosorbent assay (ELISA)-based method (Ref. 63). Ten of the 12 samples, representing all 3 brands of oat products, were reported to contain an amount of gluten ranging from 12 to 1861 ppm, depending upon the individual sample and brand tested. Thompson concluded that none of these brands could be considered a reliable source of oats free of potentially harmful gluten from other grains. In another study, Hernando and colleagues (Ref. 64) collected 108 samples of commercial oat products (e.g., rolled oats, oat flakes, and oat flours) from Europe, the United States and Canada. The samples were analyzed for gluten from wheat, rye, and barley using an ELISA-based method. In addition, analysis of the samples by polymerase chain reaction
(PCR)was used to identify the particular grains present. Consistent with the previous findings of Thompson, the presence of gluten from other grains was found to be widespread. Seventy-nine percent of the oat samples were reported to contain gluten from wheat, rye, and/or barley at a level ranging from less than 3 to 8,000 ppm gluten (Ref. 64). Sixty-one percent of the samples contained more than 200 ppm gluten. Hernando and colleagues also reported barley to be the predominant grain present. Although there appears to be widespread commingling of oats with other grains, it appears that this commingling is preventable. Two manufacturers who submitted written responses to FDA's 2005 public meeting on gluten-free food labeling report that the oats they market in the United States do not contain gluten from wheat, rye, and barley (Refs. 65 and 66). Examples of the types of special measures reported by one or both manufacturers to ensure that their oats do not contain gluten from wheat, rye, and barley are as follows:
(1)Contracting with farmers who are experienced with growing crops to ensure their purity;
(2)using only oat seed certified to be pure;
(3)planting oats only in fields that have not produced wheat, rye, or barley in either 2 or 3 years;
(4)establishing a 25- or 30-foot buffer zone separating their oat crops from other crops;
(5)conducting periodic inspections to remove any stray wheat, rye, or barley plants growing in their fields;
(6)using only dedicated or thoroughly cleaned equipment and facilities to harvest, transfer, store, and process their oats;
(7)having an independent lab test samples of their freshly harvested and milled oats, using an ELISA-based method designed to detect gluten naturally occurring in wheat, rye, and barley; and
(8)milling their oats in dedicated facilities that either only mill oats or only mill oats and soy. D. FDA's Prior Statements on Gluten-Free Food Labeling Currently, there is no FDA regulation that specifically defines the term “gluten-free.” In the preamble to a final rule on the declaration of ingredients on food packaging published in the **Federal Register** of January 6, 1993 (58 FR 2850 at 2864), FDA advised that the term “gluten-free” can be used in the labeling of foods, provided that when such claim is used, it is truthful and not misleading. Generally, and absent regulations to the contrary, FDA would regard a claim that a food is “free” of a substance as false or misleading if the food contains that substance. FDA also noted that the term “gluten-free” may be misleading when the food ordinarily does not contain gluten. Although FDA did not define the term “gluten,” FDA referred to the grains wheat, barley, rye, oats and millet as those “which commonly contain gluten” (FR 2850 at 2863). FDA's view that the term “gluten-free” may be misleading when a food is inherently free of gluten is consistent with FDA regulations governing the use other “free” claims. FDA has issued regulations that establish requirements for a “free” labeling claim made about a food inherently free of calories (§ 101.60(e)(ii) (21 CFR 101.60(e)(ii)), of nutrients (e.g., sodium, § 101.61(b)(1)(iii) (21 CFR 101.61(b)(1)(iii)) and fat, § 101.62(b)(1)(iii) (21 CFR 101.62(b)(1)(iii)), and of other food components (e.g., cholesterol, § 101.62(d)(1)(ii)(E)). FDA considers “calorie-free,” “sodium-free,” “fat-free,” and “cholesterol-free” labeling claims made for a food that inherently does not contain these substances to be misleading to consumers without additional clarifying wording indicating that all foods of the same type, not just the brand of food bearing that “free” labeling claim, are also free of the stated substance. Consistent with how FDA has regulated other “free” claims, the agency would consider a gluten-free labeling claim made for a food that inherently does not contain gluten to be misleading if it is not accompanied by additional wording to clarify that all foods of the same type, not just the brand of food bearing the gluten-free claim, are also free of gluten. As discussed elsewhere in this preamble, FDA proposes to define prohibited grain to include all species of wheat, rye, barley, and their crossbred hybrids. FDA's proposed definition of prohibited grain would exclude all other grains, including oats and millet. E. Food Allergen Labeling and Consumer Protection Act of 2004 and Related Activities 1. Food Allergen Labeling and Consumer Protection Act of 2004 FALCPA, Title II of Public Law 108-282, was enacted on August 2, 2004. Section 206 of FALCPA directs the Secretary of Health and Human Services (HHS), in consultation with appropriate experts and stakeholders, to issue a rule to define, and permit use of, the term gluten-free on the labeling of foods. FALCPA directs the issuance of a proposed rule by no later than 2 years after the law's enactment date, and a final rule by no later than 4 years after the law's enactment date. FDA is publishing this proposed rule in response to this directive. 2. FDA's Threshold Working Group and Its Report on Approaches to Establish Thresholds FALCPA does not require FDA to establish a threshold level for gluten. Nonetheless, an important scientific issue associated with the issuance of this proposed rule is the potential existence of a threshold level below which it is unlikely that an individual with celiac disease would experience an adverse health effect. To address this issue, among others, FDA established an internal, interdisciplinary group (the Threshold Working Group) to review the scientific literature on the issue of a threshold level for gluten. The Threshold Working Group's draft report, *Approaches to Establish Thresholds for Major Food Allergens and for Gluten in Food* (the draft Thresholds Report) (Ref. 67), summarized the current state of scientific knowledge with respect to a dose-response relationship for gluten, and presented the following four potential approaches that FDA might consider in establishing such a threshold level, if the agency chose to do so (Ref. 67, pp. 2 and 38 through 41): • *Analytical methods-based* —thresholds are determined by the sensitivity of the analytical method(s) used to verify compliance. • *Safety assessment-based* —“safe” level is calculated using the No Observed Adverse Effect Level (NOAEL) from available human challenge studies, applying an appropriate “uncertainty factor” multiplier to account for knowledge gaps. • *Risk assessment-based* —examines known or potential adverse heath effects resulting from human exposure to a hazard; quantifies the levels of risk associated with specific exposures and the degree of uncertainty inherent in the risk estimate. • *Statutorily-derived* —uses an exemption articulated in an applicable law and extrapolates from that to other potentially similar situations. The report also noted that any decisions on approaches to establish a threshold for gluten likely would require consideration of additional factors not addressed in the report, such as ease of compliance and enforcement, concerns of stakeholders (i.e., industry, consumers, and other interested parties), economics (e.g., cost/benefit analysis), trade issues, and legal authorities. A notice of availability for the draft Thresholds Report was published in the **Federal Register** (70 FR 35258, June 17, 2005) and the report was made available through FDA Docket No. 2005N-0231 and the Center for Food Safety and Applied Nutrition (CFSAN) Web site ( *http://www.cfsan.fda.gov/~dms/alrgn.html* ). FDA requested that interested persons submit comments and any scientific data or other information relevant to the draft Thresholds Report to the docket during a 60-day comment period ending August 16, 2005. The Threshold Working Group considered the comments, data, and information submitted, and made appropriate revisions to the Thresholds Report. On May 25, 2006, FDA posted its response (Ref. 68) to the comments, data, and other information that the agency received on its draft Thresholds Report ( *http://www.cfsan.fda.gov/~dms/alrgcom.html* ). FDA also posted the revised Thresholds Report (Ref. 69) ( *http://www.cfsan.fda.gov/~dms/alrgn2.html* ). Both of these documents are dated March 2006. 3. Food Advisory Committee Meeting of July 13 through 15, 2005 In the **Federal Register** of May 23, 2005 (70 FR 29528), FDA announced that FDA's Food Advisory Committee
(FAC)would be holding a public meeting on July 13 through 15, 2005, to evaluate the draft Thresholds Report. One purpose of the meeting was for the FAC to determine whether the four approaches considered in the draft Thresholds Report for establishing a threshold level for gluten were scientifically sound. FDA invited experts to address a number of specific issues related to sensitivities to gluten. In addition, FDA invited interested members of the general public to present their comments and any scientific data or other information relevant to the issues pending before the FAC. During the public meeting, the FAC heard presentations from invited experts on the diagnosis and treatment of celiac disease, the quality of life issues faced by those who have celiac disease and their families, the relationship between gluten proteins in various grains and celiac disease, analytical methods for detecting and measuring the levels of gluten in food, the value and use of prospective and retrospective gluten tolerance studies, and a summary of existing national and international definitions of gluten-free standards for food labeling. Further, members of the general public, including those representing trade associations, industry, consumers, and other stakeholders, gave brief presentations before the FAC to share their perspectives on some of the same topics addressed by the invited experts. Approximately 140 persons attended the FAC meeting. The speaker presentations, public comments, FAC discussions, and the FAC responses to a set of specific questions and the charge to the FAC posed by CFSAN are recorded in the transcript of the meeting, which is available through the FDA Docket No. 2005N-0231 and is posted at CFSAN's Web site ( *http://www.fda.gov/ohrms/dockets/ac/cfsan05.html* ). Copies of the transcript materials that specifically address the topics of celiac disease and a gluten threshold level are also available through the FDA Docket No. 2005N-0279 pertaining to this rulemaking. A summary of the FAC responses to the questions is provided in the Summary Minutes (Ref. 70). The FAC concluded that the draft Thresholds Report “includes a comprehensive evaluation of the currently available data and descriptions of all relevant approaches that could be used to establish [a] threshold * * *for gluten in food” (Ref. 70, p. 1). The FAC also identified the risk-assessment approach as the strongest of the four approaches proposed in the draft Thresholds Report, assuming the availability of sufficient data (Ref. 70, p. 1). FDA received about 20 public responses, each containing one or more comments, to the FAC meeting and to the notice of availability and request for comments on the draft Thresholds Report. (Some of these responses concerned food allergens and are not relevant to this proposal.) Approximately half of the total number of responses mentioned wheat or gluten, and the majority of the responses submitted about gluten addressed issues or provided data directly related to the report's suggested approaches to establishing a threshold level for gluten. Pertinent comments were considered by FDA in the development of this proposed rule. All written responses submitted to FDA about the FAC meeting and the draft Thresholds Report are available through FDA Docket No. 2005N-0231, and copies of those responses that specifically mentioned wheat or gluten are also available through FDA Docket No. 2005N-0279. 4. Gluten-Free Food Labeling Public Meeting of August 19, 2005 In the **Federal Register** of July 19, 2005 (70 FR 41356), FDA announced that it would be holding a public meeting on August 19, 2005, to discuss the topic of gluten-free food labeling. Interested persons were given until September 19, 2005, to comment on a list of specific questions concerning food manufacturing, analytical methods, and consumer purchasing practices and views about gluten-free foods (70 FR 41356 at 41357). In addition, FDA invited experts to address these issues at the meeting, and invited members of the general public, including individuals with celiac disease and their caregivers, to share their views about foods produced and labeled as “gluten-free.” More than 80 persons attended the public meeting on gluten-free food labeling. In response to the notice and public meeting, FDA received more than 2,400 responses, each containing one or more comments, about the public meeting or the list of questions cited in the notice announcing the meeting. The vast majority of these responses were from individuals with celiac disease, their caregivers, and celiac disease associations, with a much smaller number of responses being from the food industry. All written responses submitted to FDA in response to the gluten-free public meeting and the questions posed in the corresponding **Federal Register** meeting notice are available through the FDA Docket No. 2005N-0279. Most of the consumers' comments said that they appreciate and use gluten-free labeling claims to identify packaged foods they can eat when trying to avoid gluten. Many consumers stated that a gluten-free labeling claim makes it easier to grocery shop, saving the consumers both time and the frustration experienced when reading often lengthy and complicated ingredients lists that they stated they do not understand. Many consumers also stated that they currently purchase only or primarily packaged foods bearing a gluten-free labeling claim, and that a standardized definition of the term gluten-free for foods marketed in the United States would provide them with more assurance that foods bearing this claim are appropriate for individuals trying to avoid gluten. The comments reflected a consensus of opinion among individuals with celiac disease and the organizations, which represent them that wheat, rye, and barley should be excluded from any products labeled as gluten-free. However, opinions expressed in comments from these individuals and organizations varied with respect to whether oats should be excluded from any products labeled as gluten-free. Industry comments indicated that currently there is no universal understanding among manufacturers of what the term gluten-free means and there is no uniform industry standard for producing foods bearing this labeling claim. Several industry comments expressed the opinion that a standardized definition for gluten-free could assist industry by promoting fair competition among packaged foods marketed as gluten-free in the United States, because all manufacturers would have to adhere to the same requirements if they label their products gluten-free. Based upon comments that FDA received during this public meeting or that were submitted in writing to the related FDA Docket No. 2005N-0279, FDA believes that a uniform definition of the term gluten-free would prevent confusion and uncertainty among both consumers and food manufacturers about what this food labeling claim means. II. Proposed Rule A. Legal Basis Section 206 of FALCPA directs the Secretary of HHS, in consultation with appropriate experts and stakeholders, to issue a proposed rule to define, and permit use of, the term “gluten-free” on the labeling of foods. FDA has authority to issue this proposed rule under sections 403(a)(1), 201(n), and 701(a) of the act (21 U.S.C. 343(a)(1), 321(n), and 371(a). Section 403(a)(1) of the act states that, “A food shall be deemed to be misbranded if its labeling is false or misleading in any particular.” In determining whether food labeling is misleading, section 201(n) explicitly provides for consideration of the extent to which the labeling fails to reveal facts “material with respect to the consequences which may result from the use of the [food] to which the labeling * * *relates under * * *such conditions of use as are customary or usual.” Section 701(a) of the act vests the Secretary (and by delegation, FDA) with authority to issue regulations for the efficient enforcement of the act. As directed by FALCPA, FDA is proposing to define the term “gluten-free” for voluntary use in the labeling of foods. FDA is also proposing to define various terms corresponding to certain specified grains and proteins that would be prohibited from use as ingredients or sources of ingredients used to make a food bearing a “gluten-free” labeling claim. Further, FDA is proposing to specify how a voluntary gluten-free labeling claim must be worded for oats and for other foods that inherently do not contain any gluten. Any use of the term “gluten-free” in the labeling of food that does not conform to the proposed regulatory definitions and requirements would render that food misbranded. In enacting FALCPA, Congress recognized the importance to individuals with celiac disease of avoiding gluten (FALCPA, section 202(6)(B)). To address this issue, section 206 of FALCPA directs FDA to issue a regulation to define and permit use of the term “gluten-free.” As discussed elsewhere in this preamble, currently there is neither a regulatory definition of the term “gluten-free,” nor is there agreement among manufacturers or consumers as to what this term means. In the course of consulting with experts and stakeholders, FDA has learned that different manufacturers have different and inconsistent definitions of the term “gluten-free.” Consumers with celiac disease and their caregivers, who rely on “gluten-free” labeling claims to make purchasing decisions, believe that a standardized definition of the term is needed to ensure that those consumers know what to expect when purchasing foods labeled as gluten-free. Therefore, FDA believes that establishing a definition of the term “gluten-free” and uniform conditions for its use in the labeling of foods is needed to ensure that individuals with celiac disease are not misled and are provided with truthful and accurate information with respect to foods so labeled. B. Definitions and Criteria for the Use of the Term Gluten-Free in Food Labeling 1. Definitions of the Terms “Prohibited Grains” and “Gluten” To facilitate proposing a definition of the term “gluten-free,” FDA proposes to also define the terms “gluten” and “prohibited grains.” FDA proposes in § 101.91(a)(2) to define the term “gluten” to mean the proteins that naturally occur in a prohibited grain and that may cause adverse health effects in persons with celiac disease (e.g., prolamins and glutelins). FDA proposes in § 101.91(a)(1) to define the term “prohibited grain” to mean any of the following grains or their crossbred hybrids (e.g., triticale, which is a cross between wheat and rye):
(1)Wheat, meaning any species belonging to the genus *Triticum* ;
(2)rye, meaning any species belonging to the genus *Secale* ; and
(3)barley, meaning any species belonging to the genus *Hordeum* . As discussed in section I.C of this document, the scientific literature reports general agreement among celiac disease experts that naturally occurring prolamins or glutelins in wheat, rye, barley, and their crossbred hybrids can cause serious adverse health effects in individuals with celiac disease and should be excluded from their diet. FDA is not proposing to include oats in the definition of a prohibited grain. As discussed in section I.C.3 of this document, the unconditional exclusion of oats from the diet of individuals with celiac disease is not supported by the *National Institutes of Health Conference Development Conference Statement on Celiac Disease* (Ref. 1) or by the American Dietetic Association (Ref. 58). FDA recognizes that a small percentage of individuals with celiac disease may not be able to tolerate some of the proteins that naturally occur in oats. However, it appears that a great majority of individuals with celiac disease can tolerate a daily intake of a limited amount (e.g., 50 grams) of oats that are free of gluten from wheat, rye, barley or their crossbred hybrids. Oats are reported to add variety, taste, satiety, dietary fiber, and other essential nutrients to the diet of individuals with celiac disease; thereby making their diet more nutritious and appealing (Refs. 44, 51, 56, and 71). Inclusion of oats in the diet of individuals with celiac disease who can tolerate oats may therefore result in the improved nutritional and health status of those individuals (Refs. 55 and 71). According to comments FDA received in response to its August 2005 public meeting on gluten-free labeling, at least two food manufacturers can produce oats that do not contain gluten from wheat, rye, barley, or any of their cross-bred hybrids. Allowing such oats to bear a gluten-free labeling claim would make them easier to identify and perhaps would encourage other manufacturers to produce such oats. Conversely, including oats in the definition of prohibited grain could eliminate any incentive for manufacturers to produce oats free of gluten from other grains because those manufacturers would have no way of distinguishing their products in the marketplace. FDA requests comments on whether the agency should include oats in the definition of a prohibited grain. 2. Definition of the Term “Gluten-Free” FDA proposes in § 101.91(a)(3) to define the claim “gluten-free” to mean that a food bearing the claim in its labeling does not contain any of the following:
(1)An ingredient that is a prohibited grain;
(2)an ingredient that is derived from a prohibited grain and that has not been processed to remove gluten;
(3)an ingredient that is derived from a prohibited grain and that has been processed to remove gluten, if the use of that ingredient results in the presence of 20 ppm or more gluten in the food (i.e., 20 micrograms or more gluten per gram of food); or
(4)20 ppm or more gluten. Examples of a prohibited grain include, but are not limited to, barley, common wheat, durum wheat, einkorn wheat, emmer wheat, kamut, rye, spelt wheat, and triticale. Examples of ingredients that are derived from a prohibited grain and that have not been processed to remove gluten include, but are not limited to: • Farina, flour made from any of the proposed prohibited grains, graham, and semolina; • Hydrolyzed wheat protein, vital gluten, wheat bran, and wheat germ; and • Barley malt extract or flavoring and malt vinegar. Because these ingredients are derived from a prohibited grain and have not been processed to remove gluten, they are presumed to contain gluten. Examples of ingredients that are or are sometimes derived from a prohibited grain and processed to remove gluten include, but are not limited to: • Food starch—modified (modified food starch); and • Wheat starch. Although these ingredients have been processed to remove gluten, FDA recognizes that there may be different methods of deriving these ingredients, and that some methods may remove less gluten than others. Therefore, FDA proposes to prohibit a food that contains one of these ingredients from bearing a gluten-free labeling claim if the use of the ingredient results in the presence of 20 ppm or more gluten in the food. A food may contain 20 ppm or more gluten even though the food does not contain an ingredient derived from a prohibited grain. For example, a food that contains an ingredient derived from oats may contain 20 ppm or more gluten if the oats were commingled with a prohibited grain during their harvest, transport, or storage. FDA believes that manufacturers who elect to use the labeling claim “gluten-free” should make certain that foods so labeled do not contain 20 ppm or more gluten, regardless of whether or not those foods contain an ingredient that is derived from a prohibited grain. Under proposed § 101.91(b)(1), a food that bears the claim “gluten-free” or similar claim in its labeling and fails to meet the conditions specified in the proposed definition of “gluten-free” would be deemed misbranded. 3. Use of the Term Gluten-Free in the Labeling of Foods That Inherently Do Not Contain Gluten FDA proposes in § 101.91(b)(2) to deem misbranded any food, with the exception of a food made from oats, that does not inherently contain any gluten from a prohibited grain and that bears the claim “gluten-free” in its labeling, unless the food complies with the following two requirements:
(1)The wording of the claim in the labeling of the food clearly indicates that all foods of the same type, not just the brand bearing this labeling claim, are gluten-free (e.g., “milk, a gluten-free food,” “all milk is gluten-free”) and
(2)the food does not contain 20 ppm or more gluten. Examples of foods that inherently do not contain gluten include, but are not limited to: • Different types of milk not flavored with ingredients that contain gluten (e.g., fresh fluid whole, low fat and nonfat milks; evaporated milk; nonfat dry milk; sweetened condensed milk); • 100 percent fruit or vegetable juices; fresh fruits and vegetables that are not coated with a wax or resin that contains gluten; and frozen or canned fruits and vegetables not made with added ingredients that contain gluten; and • A variety of single ingredient foods, e.g., butter; eggs; lentils; legumes like dried beans and peas, peanuts, and soybeans; seeds like flax, poppy and sesame; tree nuts like almonds, pecans, and walnuts; non-gluten containing grains like corn, millet and rice; fresh fish like cod, flounder and haddock; fresh shellfish like clams, lobster, and octopus; honey; and water, including bottled waters like distilled and spring. FDA's proposed requirement for the labeling of foods, other than foods made from oats, that inherently do not contain gluten is consistent with the general principles established at § 101.13(e)(2) (21 CFR 101.13(e)(2)) for existing FDA regulations on “free” labeling claims made for foods inherently free of calories, nutrients (e.g., sodium, fat), and other food substances (e.g., cholesterol). If a single brand of food inherently free of the substance that is the subject of its “free” labeling claim does not also include additional qualifying language, consumers may mistakenly assume that only that particular brand of the food is free of the substance and may not understand that other brands of the same type of food that do not make a “free” labeling claim are also free of the substance (Ref. 72). Therefore, FDA views the use of a gluten-free labeling claim for a food inherently free of gluten to be potentially misleading without the inclusion of additional qualifying language. Although oats are inherently free of gluten as defined in this proposed rule, FDA proposes in § 101.91(b)(3) to deem misbranded a food made from oats that bears a gluten-free labeling claim if the claim refers to all such foods as being gluten-free or if it contains 20 ppm or more gluten. By “food made from oats,” FDA means oats, any food that contains oats, and any food that contains any ingredient derived from oats. The proposed gluten-free labeling claim restriction in § 101.91(b)(3) is based on evidence of the presence of gluten from prohibited grains in a number of commercially available brands of foods made from oats, as discussed in section I.C.3 of this document. In light of that evidence, FDA believes that a gluten-free labeling claim that suggests that all foods made from oats are gluten-free would be misleading. The agency is interested in receiving comments and scientific information on whether a gluten-free claim on an inherently gluten-free food, other than foods made from oats, would be misleading in the absence of additional qualifying language. In addition, FDA is interested in receiving comments and scientific information on whether the proposed examples of how a claim should be worded in the labeling of a food inherently free of gluten (e.g., “milk, a gluten-free food,” “all milk is gluten-free”) would effectively inform consumers that all brands of the same type of food are also free of gluten, or whether there are more appropriate ways to communicate this message to consumers. Further, FDA requests comments on the agency's proposal to restrict the types of gluten-free labeling claims that can be made for oats. 4. Use of the Analytical Methods-Based Approach in This Proposed Rule to Set a Threshold Level of 20 ppm to Define the Term Gluten-Free As discussed in section I.E.2 of this document, the draft Thresholds Report describes four approaches FDA could use to establish a threshold level for gluten that could be the basis for decisions on whether to use the term “gluten-free” on product labels (Refs. 67, pp. 2, 38 through 41, and 54 through 61). The draft Thresholds Report concludes that it currently is not possible for FDA to use the quantitative risk assessment-based approach due to the lack of sufficient data from human clinical trials and the lack of sufficient data on exposure, and that the statutorily-derived approach is not viable in the absence of applicable statutory provisions (Refs. 67, pp. 4, 60, and 61). The draft Thresholds Report concludes that two approaches are viable for FDA to establish a threshold level for gluten:
(1)The safety assessment-based approach and
(2)the analytical methods-based approach (Ref. 67, pp. 4 and 57 through 60). The revised Thresholds Report identifies the same four approaches and conclusions (Ref. 69, pp. 2, 4, 42 through 45, and 61 through 65). FDA is planning to conduct a safety assessment for gluten that is consistent with the safety assessment-based approach described in the draft and revised Thresholds Reports (Ref. 67, pp. 38, 39, and 58 through 60 and Ref. 69, pp. 42, 43, and 62 through 64). FDA requests comments providing data relevant to the planned safety assessment, including in particular clinical research and studies designed to measure chronic exposure, that satisfy the data quality criteria discussed in the revised Thresholds Report. We intend to publish a notice in the **Federal Register** seeking comment on the draft safety assessment and its potential use in the final rule, and will consider public and peer-review comments in revising the safety assessment, as appropriate. In developing a final rule on gluten-free labeling, we intend to consider the safety assessment as well as comments received in response to this proposed rule and the notice concerning the safety assessment. Further, as noted in both the draft and revised Thresholds Reports, FDA's establishment of a threshold level for gluten may require consideration of other factors not addressed in that report, such as ease of compliance and enforcement, stakeholder concerns, economics, trade issues, and legal authorities (Ref. 67, p. 41 and Ref. 69, p. 45). This may be true regardless of which approach FDA uses to establish a threshold level for gluten in the final rule (e.g., an analytical methods-based approach or a safety assessment-based approach). Pending the receipt of comments submitted in response to this rulemaking and the outcome of the planned safety assessment, FDA is currently proposing to use the analytical methods-based approach to establish a threshold level of 20 ppm gluten (i.e., a food labeled gluten-free cannot contain 20 ppm or more gluten) as one of the criteria for defining the term “gluten-free.” Given the current unavailability of appropriate test methods that can reliably and consistently detect gluten at levels below 20 ppm, 2 FDA tentatively concludes that gluten-free labeling on a food that contains less than 20 ppm gluten would be neither false nor misleading, so long as it conforms to other pertinent requirements of this proposed rule. 2 The revised Thresholds Report (Ref. 69, pp. 59 and 60) identifies specific criteria for evaluating gluten detection analytical methods that are appropriate for establishing a gluten threshold level based upon an analytical methods-based approach. In reviewing the available methods that meet all of the stated criteria (Ref. 73), FDA has tentatively concluded that currently there are no available and appropriate test methods that can reliably and consistently detect gluten in a variety of food matrices at levels below 20 ppm. Based upon the current state of technology concerning available and appropriate analytical methods that can detect one or more gluten proteins naturally occurring in wheat, rye, and barley, FDA has tentatively determined that ELISA-based methods can be used to reliably and consistently detect gluten at a level of 20 ppm in a variety of food matrices, including both raw and cooked or baked foods (Ref. 73). ELISA-based methods detect the prolamins in wheat, rye, and barley, which can serve as a biomarker for the presence of those grains, their cross-bred hybrids, or their other naturally occurring proteins. FDA is tentatively considering using an ELISA-based method that has been validated in Europe at the 20 ppm gluten detection level and has been published in the peer-reviewed scientific literature (Ref. 74). FDA has been advised that this method is currently under review by AOAC INTERNATIONAL (Ref. 75). In addition, we are aware that an evaluation of other ELISA-based methods that detect gliadin, a gluten protein, was recently published in the peer-reviewed scientific literature (Ref. 76). FDA requests comments on the appropriateness of 20 ppm gluten as the proposed threshold level as determined using an ELISA-based method. As new, more sensitive methods of detection are developed, use of a methods-based approach, if not tempered by consideration of other factors, could result in a threshold level that is lower than the proposed threshold level of 20 ppm gluten. For example, the manufacturer of a test kit that uses an ELISA-based method that has been validated at the 160 ppm gluten detection level (Ref. 77) is seeking validation of that method at the 5 ppm gluten detection level (Ref. 78). Given the possibility that new, more sensitive methods of detection will be developed in the near future, FDA requests comments on what effects the adoption of a lower threshold level would have on individuals with celiac disease and on industry. FDA is interested in receiving scientific data or other information that addresses the question of whether the adoption of a lower threshold level would be of benefit to individuals with celiac disease. FDA is also interested in receiving comments and supporting data on whether the use of a lower threshold level could reduce the commercial availability in the United States of foods labeled gluten-free and whether that reduced availability could negatively impact individuals with celiac disease (e.g., by making it more difficult for them to comply with dietary restrictions, perhaps leading to increased health risks). In addition, FDA requests comments on whether a safety assessment or risk assessment that addresses gluten threshold levels for individuals with celiac disease has been conducted by other entities. FDA also requests information on any gluten tolerance studies that have been published in the scientific literature since March 2006 when FDA posted the revised Thresholds Report. FDA recognizes that even those foods that comply with the proposed threshold level of 20 ppm gluten nonetheless may contain some gluten up to 20 ppm. FDA questions whether the potential presence of some gluten up to 20 ppm would be a material fact that, if omitted, would make a “gluten-free” claim potentially misleading. FDA requests comments on whether the use of additional qualifying language (e.g., “does not contain 20 ppm or more gluten per gram of food”) would be necessary to inform individuals with celiac disease that a food labeled as gluten-free nonetheless may contain the amount of gluten permitted under whatever threshold level is established in the final rule. FDA is aware that at least one other regulatory body outside the United States has developed a two-tiered approach to gluten-related food labeling. Australia and New Zealand have established standards for “gluten-free” (meaning no detectable gluten) and “low-gluten” (meaning no more than 20 milligrams gluten per 100 grams of the food, which is equivalent to no more than 200 ppm gluten in the food) (Ref. 79). As discussed in section III.C.6 of this document, one regulatory option (Option Six) was to develop a 2-tiered approach to a gluten-related food labeling in the United States. However, it is unclear what the scientific basis for such an approach would be; a safety assessment could provide a basis for a threshold, as described in the draft and revised Thresholds Reports, but would not provide a basis for a two-level approach. Thus, FDA tentatively concludes that this approach is not feasible because we do not have sufficient scientific data to recommend a specified level of gluten to define the term “low gluten.” In the absence of such information, use of the term “low gluten” in the labeling of food could make that labeling potentially misleading. FDA requests comment on this tentative conclusion, including comment on a possible scientific basis for setting a level of gluten to be defined as “low gluten.” Also, in the absence of a regulatory definition of “low-gluten,” FDA is concerned that different and inconsistent definitions of that term may be developed and used by industry, and that use of the term under such circumstances could mislead consumers. Therefore, FDA is considering whether it is necessary to prohibit use of the claim “low-gluten” and similar claims in the labeling of foods. FDA requests comment on this potential prohibition. C. Compliance and Enforcement of an FDA Gluten-Free Food Labeling Claim As previously discussed, FDA has identified a method that can reliably detect the presence of 20 ppm gluten in a variety of food matrices, including both raw and cooked or baked products. However, determinations of compliance with the proposed regulation need not be based on analysis of a food. In the enforcement of FDA-regulated food labeling claims, the agency routinely uses a variety of techniques, such as label reviews, onsite inspections of food manufacturers, and analysis of food samples. FDA does not necessarily analyze a food when other information or evidence exists that would enable the agency to determine that the food is misbranded. For example, if flour derived from spelt or kamut, which are species of wheat, is declared in the ingredient list for a bread labeled gluten-free, FDA would not have to analyze the product to deem it misbranded. This is because all flours made from cereal grains contain those grains' naturally occurring proteins. Likewise, if an FDA inspector were to observe the manufacturing of such a bread with spelt or kamut flour, the agency would not have to analyze the product to deem it misbranded. There are circumstances when FDA may seek to analyze a food to determine if it is misbranded, such as in cases when FDA investigates complaints from consumers who report experiencing adverse health effects after eating a product, and an FDA label review or onsite inspection of the manufacturing facility is insufficient to identify whether there is a problem with the food. For example, an ingredient may not have been declared on the food label or a declared ingredient may inadvertently contain an undeclared substance. In such cases, an analysis of the food may be the only way to identify the presence of the substance that is the subject of the “free” labeling claim. III. Preliminary Regulatory Impact Analysis FDA has examined the impacts of this proposed rule under Executive Order 12866, the Regulatory Flexibility Act (5 U.S.C. 601-612), and the Unfunded Mandates Reform Act of 1995 (Public Law 104-4). Executive Order 12866 directs agencies to assess all costs and benefits of available regulatory alternatives and, when regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety, and other advantages; distributive impacts; and equity). We believe that this proposed rule is not a significant regulatory action under the Executive Order. A. Need for This Regulation FALCPA directs the Secretary of HHS to issue, in consultation with appropriate experts and stakeholders, a rule to define and permit use of the term “gluten-free” on the labeling of foods. B. Proposed Regulatory Options We considered several regulatory options or alternatives:
(1)Take no action;
(2)take the proposed action—i.e., do not permit firms to make gluten-free claims on foods containing
(a)the prohibited grains;
(b)ingredients derived from the prohibited grains that have not been processed to remove the gluten;
(c)ingredients derived from the prohibited grains that have been processed to remove gluten, if the use of such ingredients results in the presence of gluten in the food at a level of 20 ppm or more; or
(d)20 ppm or more gluten from any source. We are also proposing as part of this option to restrict the wording of gluten-free claims on foods that inherently do not contain gluten;
(3)take the proposed action, except enforce the prohibition when the level of gluten exceeds some specified level other than 20 ppm in situations in which the gluten that is present in the food is
(a)from ingredients derived from a prohibited grain that have not been processed to remove the gluten or
(b)from commingling;
(4)do not permit firms to make gluten-free claims on foods containing 20 ppm or more gluten, regardless of the ingredients they use to make them, and restrict the wording of gluten-free claims on foods that inherently do not contain gluten;
(5)take the proposed action, except delete the wording requirements for gluten-free claims on foods that inherently do not contain gluten;
(6)take the proposed action, but also define the food labeling claim “low gluten;” and
(7)take the proposed action, except include oats in the list of grains that we propose to prohibit in foods that firms label as gluten-free. We request comments on these options as well as suggestions for other regulatory policy options that we should consider. We will address any significant comments or suggestions in the analysis of the final rule. C. Impacts of the Proposed Regulatory Option The primary impacts of the regulatory alternatives that we discuss in the following analysis are costs for firms to make any necessary changes to food labels and the impact of any label changes on consumer search costs. A decrease in search costs is a benefit; an increase in search costs is a cost. 1. Option One: Take No Action We can only define costs and benefits relative to a baseline. We usually select the option of taking no action as the baseline because it helps readers identify the costs and benefits of actions that change the status quo. By definition, the baseline itself has no costs or benefits. This does not mean that we ignore the costs and benefits of taking no action. Instead, it means that we express the costs and benefits of taking no action in the costs and benefits of the other regulatory options. 2. Option Two: Take the Proposed Action—Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing the Prohibited Grains or Ingredients That Have Been Derived From Those Grains and Have Not Been Processed to Remove the Gluten; Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing Ingredients Derived From the Prohibited Grains That Have Been Processed to Remove the Gluten, if the Level of Gluten Is 20 ppm or Greater; Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing 20 ppm or More Gluten, Regardless of How the Gluten Got Into the Food; and Restrict Wording of Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten a. *Overview* . We are proposing to prohibit firms from making gluten-free claims on the labels of foods that contain any of the following:
(1)Ingredients that are any of the species of the grains wheat, rye, barley, or a crossbred hybrid of these grains (e.g., triticale) (these grains are collectively referred to as “prohibited grains,” a term we propose to define in this rule);
(2)ingredients that have been derived from a prohibited grain and have not been processed to remove the gluten;
(3)ingredients that have been derived from a prohibited grain and have been processed to remove the gluten, if the use of such ingredients results in the presence of gluten in the food at a level of 20 ppm or more; and
(4)20 ppm or more gluten from any source. We do not specify a particular level for the first two categories of substances because we would not need to test such products to determine the presence of gluten. Instead, we would be able to determine the presence of gluten by
(1)reading the labels of the foods bearing gluten-free claims to determine if firms declared any of the prohibited grains or ingredients derived from the prohibited grains that have not been processed to remove the gluten in the ingredient list or
(2)by conducting onsite inspections of manufacturing facilities to observe if firms were using any of the prohibited grains or ingredients derived from the prohibited grains that have not been processed to remove the gluten to make a food labeled gluten-free. Specifying a level of 20 ppm for the third and fourth categories of substances enables us to test food containing those substances to determine if they contained gluten. The third category of substances refers to ingredients that have been derived from a prohibited grain but have been processed to remove the gluten. Some common examples from among the many ingredients in this category are wheat starch, malt extract, and malt vinegar. Depending on the effectiveness of the procedures used, people may be able to remove all the gluten from those ingredients. Thus, we would not be able to determine if food that firms made using those ingredients contained gluten by simply reading the ingredient list. The fourth category of substances refers to gluten from any source including commingling with any of the prohibited grains. We would not be able to determine if food contained gluten due to commingling by reading the ingredient list. Not permitting gluten-free claims on foods that firms make using the prohibited grains and ingredients that have been derived from them and have not been processed to remove the gluten would have no impact on current labeling because we already do not permit firms to make gluten-free claims on foods that contain gluten, and any product that firms make using prohibited grains and ingredients that have been derived from them and have not been processed to remove the gluten would contain gluten. Similarly, specifying 20 ppm or more gluten as the amount of gluten that would cause a food bearing a gluten-free labeling claim to be misbranded, if the gluten that is present in the food is from ingredients that have been derived from a prohibited grain and have been processed to remove the gluten or from any other source, would have no impact on current food labeling. Although to date we have not identified a maximum level of gluten that would be permissible in a food bearing a gluten-free claim, we generally would regard a claim that a food is “free” of a substance as false or misleading if the food actually contains that substance. As we discussed earlier in this preamble, a method exists that can reliably and consistently detect the presence of gluten at a level of 20 ppm. If we were to take enforcement action against a product with a gluten-free claim under our existing regulations and policies, we would use this test to determine whether a food bearing a gluten-free claim is misbranded. Therefore, these two elements of the proposed rule do not change the status quo and cannot generate costs or benefits. We recognize that some firms may currently be making gluten-free claims on the labels of products that contain gluten at levels of 20 ppm or more. Any costs to these firms from changing product labels are not costs of this rule but of the existing statute that prohibits false or misleading labeling. We are also proposing to restrict how firms may word gluten-free claims that appear on inherently gluten-free food. In addition to the requirement that such food not contain 20 ppm or more gluten from any source, we also propose that if a food, other than a food made from oats, that inherently does not contain gluten bears a gluten-free labeling claim, then the wording of the claim must clearly indicate that all foods of the same type, not just the brand bearing this labeling claim, are gluten-free. Two examples of the wording of a claim that would meet both criteria are “milk, a gluten-free food” and “all milk is gluten-free.” Currently, we determine whether a gluten-free claim on an inherently gluten-free product is misleading on a case-by-case basis. Therefore, this element could generate both costs and benefits. We also propose that a food made from oats can bear a gluten-free labeling claim if the wording of the claim does not refer to all foods of the same type as gluten-free. This element could also generate both costs and benefits. b. *Costs* . Restricting the wording of gluten-free claims on inherently gluten-free foods could generate compliance costs because it would require firms to remove or change current gluten-free claims on inherently gluten-free foods that use wording that does not meet our proposed requirements. We searched the Food Labeling and Packaging Survey 2000 (FLAPS 2000) database for foods bearing gluten-free claims and found the following types of foods: Yeast, enriched rice drink, pad Thai noodles (rice noodles and sauce), and rice pudding. In addition, we found “wheat gluten-free” claims on yeast and a soy protein shake. We would not classify as inherently gluten-free any of the foods that we identified in FLAPS as bearing gluten-free claims because firms could formulate or manufacture those types of foods to contain gluten. Based on this information, we estimate that this element of the proposed rule would generate minimal or no relabeling costs. In addition, this element might generate increased search costs for some consumers by suppressing the use of gluten-free claims on inherently gluten-free food other than foods made from oats. The incentive for firms to use these claims increases with the ability of the claims to increase profits. Gluten-free claims that consumers interpret to refer to a particular brand probably increase that particular firm's profits more than gluten-free claims that consumers interpret to refer to general product types because such brand-specific claims provide consumers a reason to buy a particular brand of product while product-type claims only provide consumers a reason to buy any product within a given product-type category. Therefore, requiring firms to use wording that refers to general product types would reduce to some degree the incentives for firms to use gluten-free claims and, therefore, would probably reduce the number of such claims appearing on inherently gluten-free food. However, some firms may still use gluten-free claims to influence consumers choosing between general product-type categories. The cost generated by this potential reduction in the use of gluten-free claims on inherently gluten-free food depends on the usefulness of such claims for consumers. Reducing the use of gluten-free claims would not generate costs for consumers who are already aware of inherently gluten-free foods because they would not need such claims to identify those foods. However, reducing the use of gluten-free claims could generate costs for consumers who are not aware that some inherently gluten-free foods are gluten-free because they might currently use such claims to help identify those foods as foods they can eat when following a diet that does not include gluten. We do not have sufficient information to estimate this potential cost. c. *Benefits* . Restricting the wording of gluten-free claims on inherently gluten-free foods other than foods made from oats might generate benefits for some consumers by making any gluten-free claims that do appear on inherently gluten-free food more informative. These benefits would depend on the usefulness of such information for consumers. The wording restrictions would not benefit consumers who already know that inherently gluten-free foods are gluten-free either from prior knowledge or because they infer it from the existence of gluten-free claims on multiple foods within a given product category. However, the wording restrictions would benefit consumers who are unaware that certain inherently gluten-free foods are inherently free of gluten. The optimal level of informative labeling would balance the countervailing impacts of the potential reduction in the number of gluten-free claims and the increase in the information content of each gluten-free claim. We do not have sufficient information on consumers' knowledge of inherently gluten-free food or on the number of such foods that firms might choose to identify as inherently gluten-free in the future to estimate these benefits. Restricting the wording of gluten-free claims on foods made from oats might generate benefits for some consumers by making any gluten-free claim that does appear on those foods less likely to mislead consumers by implying that those foods cannot contain gluten via commingling with the prohibited grains. We do not have sufficient information on the impact on consumers of avoiding potential confusion about the possibility that foods made from oats may contain gluten via contact with the prohibited grains or on the number of foods made from oats that firms might choose to label as gluten-free in the future to estimate these benefits. d. *Summary* . Not permitting gluten-free claims on foods that firms make using the prohibited grains or ingredients that have been derived from them and have not been processed to remove the gluten would not generate costs or benefits. Similarly, not permitting gluten-free claims on foods that firms make using ingredients that have been derived from prohibited grains and have been processed to remove the gluten and on foods that contain gluten from any other source, if those foods contain 20 ppm or more gluten, would also not generate costs or benefits. Both of these proposed requirements are consistent with how we would currently enforce our existing statute that prohibits false or misleading labeling statements. Restricting the wording of gluten-free claims on foods that inherently do not contain gluten might require some firms to change product labels. However, we were unable to identify any such foods. Therefore, we estimate that these costs would be minimal. Restricting the wording of gluten-free claims on inherently gluten-free foods may also generate future costs and benefits by changing the incentives to use such claims and changing the information content of gluten-free claims on affected foods. We do not have sufficient information to quantify these potential costs and benefits. 3. Option Three: Take the Proposed Action, Except Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing Ingredients Derived From the Prohibited Grains That Have Been Processed to Remove The Gluten, if The Level of Gluten Is Some Specified Level Other Than 20 ppm, and Do Not Permit Firms to Make Gluten-Free Claims on Foods If the Level Of Gluten Is Some Specified Level Other Than 20 ppm, Regardless of How the Gluten Got Into the Food a. *Overview* . Under this option, we could specify a threshold level that was either higher or lower than 20 ppm gluten for deeming a food labeled gluten-free to be misbranded, when the gluten that is present in that food is from ingredients that have been derived from the prohibited grains and have been processed to remove the gluten or from any other source. However, we have chosen to analyze alternative levels higher than 20 ppm gluten because we do not know of any currently available and appropriate test methods that can reliably and consistently detect gluten at levels below 20 ppm. Specifying a level higher than the proposed level of 20 ppm gluten would expand the number of foods that would be eligible to bear gluten-free claims and would generate both costs and benefits. We do not need to specify precisely a level above the proposed level of 20 ppm in order to analyze this option. We note that if we were to choose this option, then we would need additional scientific data to analyze the costs and benefits of whatever level we chose. Specifying a level higher than 20 ppm gluten would not generate compliance costs for industry because gluten-free claims are voluntary and no firms would need to remove existing labeling claims that are appropriate under the statute. However, it could generate search costs for some consumers. As we discussed in section I.A of this document, the symptoms of celiac disease are highly variable among affected individuals. We don't know the reasons for this variability. Some individuals with celiac disease may be unable to tolerate whatever level of gluten we might specify. Individuals who cannot tolerate whatever level of gluten we might specify might nevertheless continue to rely on gluten-free claims to identify appropriate foods and might suffer adverse health consequences from doing so. However, we assume that most consumers who use gluten-free claims to identify appropriate foods will have been diagnosed with celiac disease and will be under a physician's care for that condition. Therefore, sensitivity to whatever level of gluten we might allow would probably be detected within a short time and these individuals would probably not continue to rely on gluten-free claims to identify appropriate foods. The more likely consequence, and the consequence that we base the remainder of our analysis upon, is that consumers who are sensitive to gluten at this higher level would no longer be able to rely on gluten-free claims to identify foods that are safe for them to eat and would need to take other steps to identify these foods. This would increase the cost for these consumers to find appropriate foods. The increased search costs might cause these consumers to conduct fewer searches for appropriate foods, which could lead them to reduce their compliance with a diet that does not include gluten and increase their risk of various adverse health effects. In addition, increased search costs for some consumers would tend to discourage firms from continuing to produce or develop new foods that contain no gluten because it could reduce their ability to inform consumers of such foods using gluten-free labeling claims, although they could continue to inform consumers about these foods in other ways. This might further reduce the compliance of these consumers with a diet that does not include gluten and generate additional adverse health effects. Under this option, the potential benefits of specifying a level greater than 20 ppm gluten, when the gluten that is present in the food is from ingredients that have been derived from a prohibited grain and have been processed to remove the gluten or from any other source, are similar in nature but opposite in effect to the costs and would accrue to different consumers. Consumers who can tolerate whatever level we specify would value our adopting that level because it might allow them to use gluten-free claims to identify a greater range of appropriate foods. This reduction in search costs could lead these consumers to conduct additional searches for appropriate foods, which could lead to them to increase their compliance with diets that do not include gluten and lower their risk of adverse health effects. In addition, the decreased search costs for these consumers would tend to encourage firms to produce or develop foods with up to the specified level of gluten, which could increase these consumers' compliance with a diet that does not include gluten and further reduce their risk of adverse health effects. We do not know how much some consumers and firms would value our specifying a level higher than 20 ppm gluten. The potential value for consumers who would benefit from this option is probably lower on a per-person basis than the corresponding potential loss for consumers who would be unable to tolerate the level of gluten allowed under the specified level because the incremental effect on a given individual's search costs of gluten-free claims appearing on some additional foods is smaller than the incremental effect of losing the use of gluten-free claims on all foods. However, we do not know how many consumers can and cannot tolerate particular levels of gluten. Therefore, we cannot draw any conclusions on the net benefits of specifying different levels. This option would include the provisions restricting the wording of gluten-free claims on inherently gluten-free food. Therefore, it would also generate the costs and benefits that we associated with those provisions in our discussion of Option Two (the proposed action) previously discussed. b. *Costs* . As we discussed in the preceding overview, this option would increase search costs for consumers who are unable to tolerate the specified level of gluten. However, as we discussed in section I of this document, accurately estimating the prevalence of celiac disease in the United States is difficult for a variety of factors. These factors also demonstrate that individuals vary for many reasons in their sensitivity to gluten. One researcher who did attempt to identify a level that all celiac patients can tolerate was Fasano (Ref. 80), who, based on data from Catassi, et al., (Ref. 81) and Collin, et al., (Ref. 82), suggested that all individuals with celiac disease may be able to tolerate between 20 and 100 ppm. (See Ref. 69 at pp. 39 and 40 for further discussion of this literature.) Some researchers address this issue in the context of wheat starch because wheat starch is a common ingredient that contains varying and sometimes very low levels of gluten (Refs. 41, 82, and 83). In general, as we discussed in both the draft and revised Thresholds Reports (Ref. 67, pp. 35 and 36 and Ref. 69, pp. 39 and 40) , the studies are inconclusive about the safety and subjective acceptability of foods that contain 20 ppm or more gluten for individuals with celiac disease. To reflect this uncertainty, we assume that 0 percent to 100 percent of consumers with celiac disease are unable or unwilling to tolerate 20 ppm or more gluten over the long term and, therefore, would be unable to continue to use gluten-free claims to identify appropriate foods under this option. Physicians have diagnosed approximately 40,000 to 60,000 people as having celiac disease in the United States (Refs. 17 and 18). We assume that physicians have prescribed a diet that does not include gluten for all consumers they have diagnosed with celiac disease. If 0 to 100 percent of these consumers cannot tolerate 20 ppm or more gluten, and if all of these consumers currently use gluten-free claims to identify appropriate foods, then 0 to 60,000 people who currently use gluten-free claims would be unable to continue to do so. We assume that only consumers who have been diagnosed with celiac disease, or those who buy food for such consumers, are currently using gluten-free claims to find appropriate foods. However, some consumers who have not been diagnosed as having celiac disease may also follow a diet that does not include gluten on their own initiative if they are experiencing symptoms of gluten intolerance. We consider this group to illustrate the consequences of our assumption that only those consumers who have been diagnosed with celiac disease use gluten-free claims on product labels. As we explained in section I.B of this document, the prevalence of celiac disease in the United States, including both symptomatic and asymptomatic individuals, ranges from about 0.4 percent to about 1.0 percent (Refs. 1 and 16), although the actual prevalence may be higher or lower. Based on this information, we assume that 0.4 percent to 1.0 percent of the United States population may have celiac disease. One study found that 40 percent of children and 60 percent of adults who were newly diagnosed with celiac disease were symptomatic (Ref. 84). Therefore, we assume the overall rate of new celiac patients who are symptomatic is between 40 percent and 60 percent. The U.S. population in August 2005 was approximately 297 million (Ref. 85). If the overall prevalence of celiac disease is between 0.4 percent and 1 percent, then approximately 1.2 million to 3.0 million people in the United States have celiac disease. If 40 percent to 60 percent of people with celiac disease have symptoms of that disease, then between 500,000 and 1.8 million people in the United States have symptoms associated with celiac disease. Earlier we noted that only 40,000 to 60,000 people in the United States have been diagnosed with celiac disease. Subtracting this number of people from the estimated number of people in the United States who have symptoms associated with celiac disease and rounding to the nearest tenth of one million implies that approximately 0.4 million to 1.8 million people have undiagnosed celiac disease and exhibit some symptoms of that disease. If some of these consumers, or those who buy food for these consumers, are currently using gluten-free claims to identify appropriate foods, then the consequences of revising the criteria for using those claims would be much greater than we have estimated based only on consumers who have been diagnosed with celiac disease. Any consumers who currently rely on gluten-free claims to identify appropriate foods and who would be unable to continue to use those claims because they cannot tolerate the level of gluten allowed under the specified level would probably need to spend additional time identifying appropriate foods. In the comments that we received during the public meeting on gluten-free food labeling, some comments said they spent up to an extra 10 hours per week shopping, while other comments said they spent five times as much time shopping as they did before they started a diet that does not include gluten. One consumer group reported that some consumers on a diet that does not include gluten said they spent an extra 30 minutes per week shopping, while other consumers said they spent twice as much time shopping as they did before they started a diet that does not include gluten (Ref. 86). This group did not report how much time the consumers spent shopping before they started a diet that does not include gluten. However, in the analysis of a previous and unrelated rule, we estimated that the average shopping time for all grocery store purchases was 46.2 minutes per week (68 FR 51738 at 51744, August 28, 2003). This average would have included those on special diets such as diets that do not include gluten. However, most people are not on special diets. Therefore, we interpret the information from this consumer group to mean that some consumers on a diet that does not include gluten who reported spending twice as much time shopping spent about 90 minutes shopping per week. This group did not report on the smallest amount of extra time that these consumers spent shopping; but, we assume that all consumers on a diet that does not include gluten would spend at least some extra time shopping. We have chosen 10 minutes per week as a reasonable estimate of this minimum amount of extra shopping time. We assume that the results reported by the consumer group are more representative of the average consumer on a diet that does not include gluten than the results reported by these individual consumers, who might not be typical of the average consumer on a diet that does not include gluten. Based on this information, we assume that being on a diet that does not include gluten increases food shopping time by 10 to 46 minutes per week. We do not know the difference in search times for those who can use gluten-free labels and those who cannot. The range in search costs that we reported previously probably includes consumers who make considerable use of gluten-free claims to identify foods and consumers who do not. Many consumers who can make considerable use of gluten-free claims probably still need to expend at least some additional time searching for foods relative to the average consumer because relatively few foods bear gluten-free claims. In addition, some consumers who use gluten-free claims to identify acceptable foods may also read ingredient lists to confirm the absence of gluten (Ref. 87). Therefore, the ability to use gluten-free claims probably leads to a relatively small reduction in extra shopping time for consumers on diets that do not include gluten. We do not have sufficient information to estimate the time savings associated with being able to use existing gluten-free claims; but, we have chosen a range of 10 to 50 percent of the difference between the low end and the high end of the range of total extra shopping time, or 0 minute to 18 minutes per week, as the extra shopping time that the ability to use gluten-free claims could reasonably be expected to eliminate. We request comments on this assumption. Consumers who cannot rely on gluten-free claims and who buy foods in conventional grocery stores probably expend the most extra time shopping because they would have to rely on ingredient lists or take other approaches to identifying appropriate foods. These consumers might need to learn more about food ingredients or use references on food ingredients. In addition, some of these consumers may call or write manufacturers to ask about ingredients. Some consumers may look up information on foods on the Internet. Finally, some of these consumers may refer to reference lists of gluten-free foods that some celiac organizations publish for this purpose. Consumers who cannot rely on gluten-free claims and who buy gluten-free foods in specialty stores or from mail order firms probably have lower search costs because some of these sources may identify foods that do not contain gluten. However, gluten-free foods are typically more expensive when purchased in specialty stores or from mail order firms than when purchased in conventional grocery stores; so, the reduction in search cost is offset by increased product prices. Based on this information, we assume that losing the ability to rely on the relatively small number of existing gluten-free labels may increase search costs by 0 to 18 minutes per week. Multiplying this range by the number of consumers who we estimated might lose the use of gluten-free labeling, 0 to 60,000, results in a potential increase in search costs of 0 to 18,000 hours per week. The average value of 1 hour of leisure time should be similar to the average value of 1 hour of working time, which was $26.05 in September 2005 for nonfarm private and State and local Government workers in the United States (Ref. 88). Therefore, we estimate the cost associated with potential increases in search costs for some consumers to be $0 to $24 million per year. If specifying a level higher than 20 ppm gluten increases product search costs for some consumers, then it may also lead those consumers to conduct fewer searches for appropriate foods, which could reduce their compliance with diets that do not include gluten. Some consumers already have difficulty following a diet that does not include gluten. One recent study said that the literature suggests that only 17 percent to 65 percent of patients who are prescribed a diet that does not include gluten manage to adhere to that diet (Ref. 89). An earlier study found that only 2 percent of 130 patients who had been diagnosed with celiac disease managed to adhere to a diet that does not include gluten (Ref. 90). One article said that poor compliance with diets that do not include gluten was at least partially due to the inconvenience of purchasing and preparing gluten-free food and the higher prices of gluten-free foods (Ref. 46). Search costs are one measure of the inconvenience of purchasing gluten-free food and probably also play a role in the higher cost of such foods. Some studies have found relatively high compliance rates for diets that do not include gluten that allow ingredients that may have trace amounts of gluten, such as wheat starch. This suggests that compliance with diets that do not include gluten that allow such ingredients may be higher than compliance with diets that do not include gluten that do not allow such ingredients. One article noted that 85 percent of celiac patients in Finland manage to adhere over the long-term to a diet that does not include gluten that allows wheat starch (Ref. 82). Similarly, one study that was conducted in Finland found that 88 percent of the patients in that study adhered to a diet that does not include gluten that allowed wheat starch (Ref. 89). These percentages are higher than the 2 percent to 65 percent compliance rates for diets that do not include gluten that we mentioned in the preceding paragraph, which were from articles that appear to have interpreted any gluten intake as a failure to comply with a diet that does not include gluten. If there is a difference in compliance rates, then part of this difference may be because gluten-intolerant consumers who can tolerate foods made with ingredients that may contain trace amounts of gluten, such as wheat starch, can more easily find appropriate and acceptable foods. For example, one study found that 13 of the 17 consumers in that study preferred a product made with wheat starch containing approximately 15 ppm gluten to foods made with rice flour or cornstarch that were entirely gluten-free (Ref. 83). On the other hand, Thompson (Ref. 41) contended that there is no evidence that compliance is higher among patients following diets that do not include gluten that allow foods made with wheat starch than among those following diets that do not include gluten that do not allow foods made with wheat starch. For example, some of the differences in the compliance rates that appear in different articles may be due to differences in the usual diets of various countries or other factors that are unrelated to whether the diet includes products that contain trace amounts of gluten such as wheat starch. Of course, factors other than search costs and product costs may affect compliance with a diet that does not include gluten. For example, one article that looked at 55 cases of persisting celiac disease caused by non-compliance with a diet that does not include gluten found that 73 percent of those patients were not aware of the continuing nature of the disease and thought they had recovered from a temporary illness, while 27 percent were aware of the continuing nature of the disease but were unable to maintain compliance without additional dietary counseling (Ref. 90). The authors suggested that the principal reason for non-compliance with a diet that does not include gluten might be the lack of morbidity associated with chronic untreated celiac disease. They noted that although a few patients had experienced lassitude, abdominal discomfort, or occasional diarrhea, the symptoms were not compelling. Another study also suggested that one potential reason for intentional non-compliance with a diet that does not include gluten is that many non-compliant patients have no symptoms and normal hematological and biochemical profiles despite notable mucosal villous atrophy and inflammation (Ref. 83). Based on this information, we assume that if this option raised search costs for some consumers, then it could lead them to decrease their compliance with a diet that does not include gluten. However, we do not have sufficient information to estimate the incremental change in compliance rates. If this option reduced some consumers' compliance with a diet that does not include gluten, then it could generate adverse health effects for those consumers. The adverse health effects associated with celiac disease are highly variable among affected individuals. We do not know the reasons for this variability, but it may depend on the age and immunological status of the individual; the amount, duration, or timing of the exposure to gluten; and the specific area and extent of the gastrointestinal tract involved by disease (Ref. 5). We discussed the adverse health effects associated with gluten consumption by celiac patients in section I.A of this document. Although decreased compliance with a diet that does not include gluten would probably generate some adverse health effects, the literature is not clear on the effect of changes in compliance on health outcomes. Based on this information, we conclude that any decrease in compliance with a diet that does not include gluten could generate additional cases of various adverse health effects. However, we cannot estimate the number of cases from this effect because we do not have sufficient information on the impact of this option on product search costs, the impact of product search costs on compliance rates, or the impact of changes in compliance rates on the risk of various adverse health effects. Finally, any reduction in the usefulness of gluten-free claims for some consumers might discourage firms from continuing to produce or developing foods with a level of gluten below the specified level. Firms could use other truthful and not misleading wording on food labels to inform consumers that a product was not made with gluten-containing ingredients or contained less than the specified level of gluten. However, these other types of label statements might not be as effective as gluten-free claims. This potential reduction in the number of foods with a level of gluten below the specified level might further increase search costs for consumers who desire such foods and might further reduce their compliance with diets that do not include gluten. We do not have sufficient information to estimate these potential costs. This option would also generate the costs that we associated with restricting the wording of gluten-free claims on inherently gluten-free food in our discussion of Option Two. We do not have sufficient information to estimate these costs. c. *Benefits* . As we discussed in the preceding overview, specifying a level higher than 20 ppm gluten might generate benefits because it would enable firms to use gluten-free claims on additional foods. Consumers who can tolerate the specified level of gluten could use gluten-free claims to more easily identify appropriate foods. We do not know how many existing foods contain particular levels higher than 20 ppm because no information is available on the amount of gluten in different grain-derived food ingredients or finished food (Ref. 69, p. 37). However, the gluten in many foods that contain trace amounts of gluten comes from ingredients such as wheat starch, malt extract, or malt vinegar. The level of gluten in wheat starch varies between 14 ppm and 740 ppm (i.e. 7 ppm to 370 ppm prolamin, which corresponds to 14 ppm to 740 ppm gluten) (Ref. 41). One small survey of 24 wheat-starch derived flours in Finland found levels of less than 20 ppm up to 160 ppm gluten (Ref. 82). The gluten levels in these products were distributed approximately as follows: 58 percent had 20 ppm or less, 13 percent had more than 20 ppm up to 40 ppm, 13 percent had more than 40 ppm up to 60 ppm, 0 percent had more than 60 ppm up to 80 ppm, 8 percent had more than 80 ppm up to 100 ppm, 0 percent had more than 100 ppm up to 140 ppm, and 8 percent had more than 140 ppm up to 160 ppm. One study analyzed gluten levels in 2 brands of wheat starch and found levels of approximately 15 ppm (0.75mg/100g) and 560 ppm (28mg/100g) (Ref. 83). One article noted that improved gluten detection techniques have demonstrated that some food made with wheat starch contains more gluten than the current Codex standard for gluten-free foods would allow (Ref. 91). Codex Standard 118-1981 (amended 1983) for gluten-free foods that is in effect today defines “gluten-free” to mean that the total nitrogen content of gluten-containing cereal grains used to make a product cannot exceed 0.05 gram nitrogen per 100 grams dry cereal grain (Ref. 92). However, some authors have attempted to estimate what this Codex restriction means in terms of ppm of gluten. One study estimates that the current Codex standard allows gluten-free products to contain up to 500 ppm (50 mg/100 g) (Ref. 93). Other studies estimate that the current Codex standard allows gluten-free products to contain up to 600 ppm gluten (60 mg/100 g) (Refs. 94 and 89). Based on this information, we assume wheat starch contains between 14 ppm and 740 ppm gluten. The level of gluten in products made with wheat starch would be significantly lower, depending upon the amount of wheat starch used in proportion to the other ingredients to make the products. However, we do not have data on the level of gluten in products made with wheat starch. Foods made with malt extract may also contain low levels of gluten (Ref. 95). Firms produce malt extract from malt grain derived from barley. Depending on the extraction technique, malt extract may contain residual amounts of gluten. One study tested some foods containing malt extract and found gluten in some samples of chocolate powder, chocolate milk, and chocolate bars, but not in breakfast cereals (Ref. 91). Foods that firms manufacture using other ingredients, such as oats, may also contain gluten if these other ingredients are commingled with grains like wheat, rye, barley, or triticale (Refs. 63 and 64). Some individuals with celiac disease may be able to tolerate levels of gluten higher than 20 ppm in ingredients such as wheat starch, malt extract, and malt vinegar. These consumers may be able to use current ingredient labeling to identify appropriate foods if firms list these types of ingredients on product labels and no other potential sources of gluten appear on the ingredient lists. However, these consumers would not always be able to use ingredient lists to determine whether a product contains gluten because some ingredients' common or usual names do not identify their food sources and some ingredients can be derived from grains that contain gluten or from grains that do not contain gluten. In some cases, firms may include ingredients containing trace amounts of gluten in other listed ingredients that have collective names such as flavors and colors. Other consumers may be able to tolerate the lower but not the higher levels of gluten that might occur in foods that contain these ingredients. These consumers would not be able to rely on current ingredient labeling because some foods that contain these ingredients could contain more than whatever amount of gluten higher than 20 ppm those consumers can tolerate. These consumers would need to take additional steps to identify foods that contain gluten at the levels they can tolerate. These additional steps might involve using references on gluten levels in different foods, calling manufacturers, or buying foods through specialty vendors that select appropriate foods or provide advice on acceptable foods. Using a level higher than 20 ppm gluten could decrease search costs for both groups of consumers, but the effect would be larger for consumers who cannot use the ingredient list to identify appropriate foods. We do not know how many consumers can tolerate any particular level of gluten. In the preceding discussion of costs, we estimated that 0 to 100 percent of the 40,000 to 60,000 consumers who we estimated to be currently on a diet that does not include gluten cannot tolerate an amount of gluten higher than 20 ppm. The corresponding estimate of the percentage of consumers who can tolerate a level of gluten higher than 20 ppm also ranges from 0 percent to 100 percent, which corresponds to 0 to 60,000 consumers. We also do not know the impact on search costs for these consumers. In the preceding cost discussion, we estimated that being on a diet that does not include gluten increases product search time by 10 to 46 minutes per week. We do not know how much of this increased time cost comes from reading ingredient labels to identify ingredients that may contain low levels of gluten or taking other steps to determine the gluten levels of foods that have these ingredients as the only sources of gluten. However, a reasonable estimate of the increased time cost is 10 to 50 percent of the difference between the low end and high end of the range of total extra shopping time, or 0 minute to 18 minutes per week after rounding. Therefore, we assume that allowing gluten-free claims to appear on foods with levels of gluten higher than 20 ppm could reduce consumers' search costs by 0 to 18 minutes per week. We request comments on this assumption. Multiplying the estimated number of consumers who have been diagnosed with celiac disease by the number of minutes results in a potential search cost savings of 0 to 18,000 hours per week. The average value of one hour of leisure time should be similar to the average value of 1 hour of working time, which was $26.05 in September 2005 (Ref. 88). Therefore, we estimate the potential benefit of reduced product search costs to be $0 to $18 million per year. Any decrease in search costs for some consumers could lead those consumers to conduct additional searches for appropriate foods, which might increase their compliance with a diet that does not include gluten. If these consumers increased their compliance with a diet that does not include gluten, then they may reduce their risk of adverse health effects. This option might also encourage firms to develop new foods with the specified level of gluten because it would improve the ability of firms to signal to consumers through the use of gluten-free labeling claims that a given product contains less than the level of gluten. The development of new foods might also further facilitate compliance with a diet that does not include gluten for consumers who can tolerate the specified level of gluten, which could lead to additional health benefits. We do not have sufficient information to estimate these benefits. This option would also generate the benefits that we associated with restricting the wording of gluten-free claims on inherently gluten-free food in our discussion of Option Two. We do not have sufficient information to estimate these benefits. d. *Summary* . The element of this option that specifies a level higher than 20 ppm gluten, when the gluten that is present in the food is from ingredients that have been derived from a prohibited grain and have been processed to remove the gluten or from any other source, would allow firms to make gluten-free claims on the labels of some foods that contain less than this level of gluten and would generate both costs and benefits. The costs would accrue to consumers who cannot tolerate the specified level of gluten and the benefits would accrue to consumers who can tolerate the specified level of gluten. We do not have sufficient information to compare the impact of this option on these two groups of consumers. Using the full range of 0 percent to 100 percent of consumers diagnosed with celiac disease as potentially falling into either group gives countervailing search costs and benefits of $0 to $18 million per year. Changes in search costs could also generate countervailing health effects for these two groups of consumers. The optimal rule from a cost-benefit perspective would balance the cost of reducing the usefulness of gluten-free claims for consumers who have a relatively high degree of sensitivity to gluten with the benefit of making gluten-free claims as useful as possible for consumers who are attempting to control their intake of gluten but are relatively less sensitive to gluten. However, we do not have sufficient information to quantify these effects or to estimate the optimal level of gluten. The element of this option that would restrict the wording of gluten-free claims on inherently gluten-free food could also generate costs and benefits. Costs would result from a potential reduction in the likelihood that firms will use gluten-free claims on inherently gluten-free food, while the benefits would result from the greater information content or the reduced potential for misleading consumers of any such claims that do appear on these foods. We do not have sufficient information to determine the net effect of these countervailing influences. 4. Option Four: Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing 20 ppm or More Gluten, Regardless of the Ingredients They Use to Make Them, and Restrict the Wording of Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten Under this option, we would allow firms to make gluten-free claims on food that they make from any type of ingredient if the food does not contain 20 ppm or more gluten. This option would generate the same costs and benefits as Option Two except that applying the 20 ppm level to food that contains one or more of the prohibited grains or that contains ingredients that have been derived from them and have not been processed to remove the gluten would represent a change from our current approach to such claims. Our current approach to claims of the form “substance X-free” is that a product that bears such a claim on its label cannot contain any level of substance X. Applying this approach to gluten-free claims implies that we do not allow firms to use gluten-free claims on foods they make from these substances regardless of the level of gluten in that food. Option Two maintains our current approach for these foods. Therefore, applying the level of 20 ppm to this food would generate costs and benefits that we did not discuss under Option Two. As a practical matter, any product that firms make from one or more of the prohibited grains will contain 20 ppm or more gluten. Therefore, the impact of applying the level to food that contains one or more of the prohibited grains is the same as the impact of our current position of prohibiting gluten-free claims on the labels of food containing these grains. Therefore, this change will not generate costs or benefits relative to the baseline. In contrast, a food that contains ingredients that have been derived from a prohibited grain and have not been processed to remove the gluten may contain less than 20 ppm gluten. Therefore, applying the level to this category of food would result in costs and benefits relative to the baseline of our current position. These costs and benefits would be in addition to the costs and benefits that we discussed under Option Two. The cost of applying the level to food that contains ingredients that have been derived from a prohibited grain and have not been processed to remove the gluten is that we would need to test the food to determine if it can bear a gluten-free claim. Enforcement actions that require testing are significantly more costly for us than enforcement actions that only require us to read ingredient lists on food labels. However, we have not analyzed the difference in costs for enforcement actions that require testing and those that do not. In addition, we cannot estimate how many times we would need to take enforcement actions against this type of food. Therefore, we cannot estimate this additional cost. This provision would not generate costs for consumers because consumers who cannot tolerate 20 ppm gluten are unable to rely on gluten-free claims to identify acceptable products under our current approach and would also be unable to do so under the proposed requirements of Option Two. This is because both our current approach to claims of the general form “substance X-free” and the approach expressed in Option Two allow firms to make gluten-free claims on products that contain less than 20 ppm gluten if the gluten that is present in the food is from a source other than an ingredient that is a prohibited grain or that has been derived from a prohibited grain and has not been processed to remove the gluten. The benefit of applying the level of 20 ppm to food that contains ingredients that have been derived from a prohibited grain and have not been processed to remove the gluten is that firms would be able to begin using gluten-free claims on this type of food, provided that the food did not contain 20 ppm or more gluten. This would generate benefits for consumers who can tolerate up to 20 ppm gluten because they would be able to rely on gluten-free claims to identify additional products. We do not have sufficient information to estimate this benefit. In summary, this option would have the same costs and benefits as Option Two except for the costs and benefits of applying the level of 20 ppm to food that contains ingredients that have been derived from a prohibited grain and have not been processed to remove the gluten. We do not have sufficient information to quantify these countervailing costs and benefits. Therefore, we cannot compare the net benefits of this option to the net benefits of Option Two. 5. Option Five: Take the Proposed Action, Except Delete Wording Requirements for Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten We could take the proposed action but delete the requirements relating to the wording of gluten-free claims on foods that inherently do not contain gluten. In that case, we would continue the status quo approach of determining whether such claims are misleading on a case-by-case basis. This would eliminate the costs and benefits of the proposed requirements that we discussed under Option Two. Therefore, this option would not generate any costs or benefits. 6. Option Six: Take the Proposed Action, But Also Define the Food Labeling Claim “Low Gluten” Under this option, we would specify requirements for a “gluten-free” labeling claim as directed by FALCPA and also specify requirements for a less restrictive “low gluten” labeling claim that firms could use on foods that contained a relatively low level of gluten at some specified level higher than 20 ppm. Firms can already use “low gluten” claims if those claims are truthful and not misleading. However, we currently do not have a position on the level of gluten that renders a “low gluten” claim truthful and not misleading. Determining an appropriate level of gluten to use in defining “low gluten” on a cost benefit basis would require, among other things, dose-response data on the health impacts of various levels of gluten on those with celiac disease. We do not have sufficient scientific data to recommend a specified level of gluten to define the term “low gluten.” Nevertheless, we address significant regulatory options in regulatory impact analyses irrespective of their feasibility. This two-tier approach could generate higher benefits than Option Two in two ways. First, by establishing explicit criteria for using “low gluten” claims, we might encourage firms to use such claims. Second, by basing the use of “low gluten” claims on a particular level of gluten, we would standardize the meaning of “low gluten” claims and make them more useful for consumers. Encouraging the use of “low gluten” claims and standardizing the level of gluten in foods bearing such claims might generate benefits because a combination of “gluten-free” claims and “low gluten” claims would provide claims that might be useful for both more sensitive and less sensitive consumers, which would increase the number of consumers who find such claims useful and decrease the number of consumers who might be unable to continue to use these claims to identify appropriate foods. However, this option may also generate costs beyond those we discussed under Option Two. First, some firms may already be using “low gluten” claims. If we define that term relative to a particular level of gluten, then some of these firms may need to change product labels. We were unable to identify any foods bearing “low gluten” labels in the FLAPS database. Therefore, we estimate that any labeling costs would be minimal. Second, the presence of two claims corresponding to different levels of gluten might confuse some consumers and lead them to consume foods with more gluten than they intend to consume. Encouraging the use of “low gluten” claims might exacerbate this potential problem. While many consumers may be familiar with “free” and “low” content claims in the context of nutrients, we have not previously defined “low” claims for other food substances that some consumers may need to totally avoid. We do not have sufficient information to estimate the costs and benefits of this option. 7. Option Seven: Take Proposed Action, Except Include Oats in the List of Grains That We Propose to Prohibit in Foods That Firms Label as Gluten-Free We could also expand the list of prohibited grains to include oats. Some consumers with celiac disease may be unable to tolerate some of the proteins that naturally occur in oats and may prefer to avoid oats in addition to avoiding the proposed prohibited grains and ingredients people make from those grains discussed in Option Two. However, other consumers with celiac disease may be able to tolerate the proteins that naturally occur in oats and, therefore, may wish to consume oats when following a diet that does not include gluten. This option could generate some relabeling costs because we currently allow firms to use gluten-free claims on foods that contain oats but do not contain gluten from commingling with a prohibited grain. These firms would need to remove the gluten-free claims from foods made from oats if we were to include oats in the list of prohibited grains. We do not know how many foods are made from oats and do not contain gluten, nor do we know the percentage of such foods that bear gluten-free claims. We searched the FLAPS 2000 database and did not find any foods that contained oats and had a gluten-free claim. Therefore, we estimate that any labeling costs would be minimal. In addition, if we included oats in the list of prohibited grains, then we would reduce the usefulness of those claims for consumers who wish to avoid gluten but can tolerate the naturally occurring proteins in oats. The increase in search costs for these consumers could be considerable because oats are a common food ingredient that can be particularly important for celiac patients who wish to avoid wheat, rye, barley, and their crossbred hybrids. An increase in search costs for these consumers may decrease their compliance with a diet that does not include gluten and possibly increase their risk of adverse health effects. However, this option would generate benefits for consumers who wish to avoid gluten and also wish to avoid oats because, if we include oats in the list of prohibited grains, then these consumers would be able to use gluten-free claims to identify appropriate foods. Expanding the usefulness of gluten-free claims for these consumers would reduce their search costs, possibly increase their compliance with a diet that does not include gluten, and possibly reduce their risk of adverse health effects. As we discussed in detail at section I.C.3 of this document, the literature is divided on the percentage of consumers with celiac disease who can tolerate oats, even when steps have been taken to prevent commingling with prohibited grains such as wheat and rye. Based on this information, we assume that some consumers with celiac disease may wish to avoid oats and that the usefulness of gluten-free claims for these consumers could depend on whether or not we include oats in the list of proposed prohibited grains. However, we do not have sufficient information to estimate the number of such consumers or the net impact of including oats in the proposed prohibited list of grains. IV. Regulatory Flexibility Analysis The Regulatory Flexibility Act requires agencies to analyze regulatory options that would minimize any significant impact of a rule on small entities. We are not proposing to change our current position with respect to the grains or proteins that we associate with gluten or the level of gluten that we would use to determine compliance with the requirements for using gluten-free claims. Further, we know of no foods that inherently do not contain gluten and that bear gluten-free claims that do not meet our proposed wording restrictions and that are produced by small entities. Therefore, the agency certifies that the proposed rule would not have a significant economic impact on a substantial number of small entities. A. Proposed Regulatory Options We considered the following regulatory options:
(1)Take no action;
(2)take the proposed action—do not permit firms to make gluten-free claims on foods containing the prohibited grains or ingredients that have been derived from them and have not been processed to remove the gluten; do not permit firms to make gluten-free claims on foods containing ingredients derived from the prohibited grains that have been processed to remove the gluten, if the level of gluten is 20 ppm or greater; do not permit firms to make gluten-free claims on foods containing 20 ppm or more gluten, regardless of how the gluten got into the food (i.e. declared ingredient, undeclared ingredient, contaminant, etc.); and restrict the wording of gluten-free claims on foods that inherently do not contain any gluten;
(3)take the proposed action, except do not permit firms to make gluten-free claims on foods containing ingredients derived from the prohibited grains that have been processed to remove the gluten, if the level of gluten is greater than some specified level higher than 20 ppm, and do not permit firms to make gluten-free claims on foods if the level of gluten is greater than some specified level higher than 20 ppm, regardless of how the gluten got into the food;
(4)do not permit firms to make gluten-free claims on foods containing 20 ppm or more gluten, regardless of the ingredients they use to make them, and restrict the wording of gluten-free claims on foods that inherently do not contain gluten;
(5)take the proposed action, except delete the wording requirements for gluten-free claims on foods that inherently do not contain gluten;
(6)take the proposed action, but also define the food labeling claim “low gluten;” and
(7)take the proposed action, except include oats in the list of grains that we propose to prohibit in foods that firms label as gluten-free. B. Impacts of the Proposed Regulatory Options on Small Entities 1. Option One: Take No Action Taking no action would have no impact on small entities. 2. Option Two: Take the Proposed Action—Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing the Prohibited Grains or Ingredients That Have Been Derived From Those Grains and Have Not Been Processed to Remove the Gluten; Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing Ingredients Derived From the Prohibited Grains That Have Been Processed to Remove the Gluten, if the Level of Gluten Is 20 ppm or Greater; Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing 20 ppm or More Gluten, Regardless of How the Gluten Got Into the Food; and Restrict Wording of Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten We are not proposing to change how we currently enforce our existing statute that prohibits false or misleading labeling other than instituting new wording requirements for gluten-free claims on foods that inherently do not contain gluten. This element may generate compliance costs for small entities. However, as we discussed in the preceding regulatory impact analysis, we know of no such foods. Therefore, we estimate that this proposed rule would generate minimal or no costs for small entities. We request information on the impact of the proposed action and all other options on small entities. 3. Option Three: Take the Proposed Action, Except Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing Ingredients Derived From the Prohibited Grains That Have Been Processed to Remove the Gluten, If the Level of Gluten Is Some Specified Level Other Than 20 ppm, and Do Not Permit Firms to Make Gluten-Free Claims on Foods If the Level of Gluten Is Some Specified Level Other Than 20 ppm, Regardless of How the Gluten Got Into the Food This option would have the same minimal impact on small entities as Option Two. As we discussed in the preceding preliminary regulatory impact analysis, we could analyze levels either higher or lower than 20 ppm, but we have chosen to analyze levels higher than 20 ppm because we do not know of any currently available and appropriate test methods that can reliably and consistently detect gluten at levels below 20 ppm. Under Option Three, specifying a level higher than 20 ppm gluten would not generate additional compliance costs for small entities because gluten-free claims are voluntary and no small firms would need to remove existing labeling claims that complied with our existing position. Therefore, we estimate that this option would also generate minimal or no costs for small entities. 4. Option Four: Do Not Permit Firms to Make Gluten-Free Claims on Foods Containing 20 ppm or More Gluten, Regardless of the Ingredients They Use to Make Them, and Restrict the Wording of Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten This option would have the same minimal impact on small entities as Option Two. Under Option Four, applying the level of 20 ppm to all foods, regardless of the ingredients firms use to make them, would not generate additional compliance costs for small entities because gluten-free claims are voluntary and no small firms would need to remove existing labeling claims that they would not already have had to remove under our existing approach to regulating gluten-free food labeling. Therefore, we estimate that this option would also generate minimal or no costs for small entities. 5. Option Five: Take the Proposed Action, Except Delete Wording Requirements for Gluten-Free Claims on Foods That Inherently Do Not Contain Gluten Taking the proposed action except deleting the wording requirements for gluten-free claims would eliminate any impact on small entities. 6. Option Six: Take the Proposed Action, but Also Define the Food Labeling Claim “Low Gluten” Establishing requirements for “low gluten” claims might generate compliance costs for small entities. As we discussed in the preceding regulatory impact analysis, we currently allow “gluten-free” claims that are truthful and not misleading. If we define “low gluten” based on a particular level of gluten, then some small firms might need to change their product labels. However, we were unable to identify any foods bearing “low gluten” claims in the FLAPS database. Therefore, we estimate that any labeling costs associated with this provision would be minimal. In addition, the provision dealing with gluten-free claims on foods that inherently do not contain gluten would have a minimal impact on small entities. Therefore, we estimate that this option would have minimal or no impact on small entities. 7. Option Seven: Take Proposed Action, but Include Oats in the List of Grains That We Propose to Prohibit in Foods That Firms Label as Gluten-Free Including oats in the list of prohibited grains may generate relabeling costs for some small firms because we currently allow firms to make gluten-free claims on foods that contain oats but do not contain any of the prohibited grains or ingredients derived from those grains provided that any gluten present is less than 20 ppm. We do not know how many small firms produce foods that contain oats but do not contain any of the prohibited grains or ingredients derived from those grains and that bear gluten-free claims. We searched the FLAPS 2000 database and did not find any foods that contained oats and bore gluten-free claims. Therefore, we estimate that any costs that might accrue to small entities from this option would be minimal. V. Unfunded Mandates Section 202(a) of the Unfunded Mandates Reform Act of 1995 requires that agencies prepare a written statement, which includes an assessment of anticipated costs and benefits, before proposing “any rule that includes any Federal mandate that may result in the expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100,000,000 or more (adjusted annually for inflation) in any one year.” The current threshold after adjustment for inflation is $115 million, using the most current
(2003)Implicit Price Deflator for the Gross Domestic Product. FDA does not expect this proposed rule to result in any 1-year expenditure that would meet or exceed this amount. VI. Executive Order 13132: Federalism We have analyzed this proposed rule in accordance with the principles set forth in Executive Order 13132. Section 4(a) of the Executive order requires agencies to “construe * * * Federal statute to preempt State law only where the statute contains an express preemption provision or there is some other clear evidence that the Congress intended preemption of State law, or where the exercise of State authority conflicts with the exercise of Federal authority under the Federal statute.” 3 Here, FDA has determined that the exercise of State authority would conflict with the proposed exercise of Federal authority under the act. 3 Because we have determined that the act preempts State law because the exercise of State authority conflicts with the exercise of Federal authority under that statute, we need not construe our statutory rulemaking authority as required by section 4(b) of the Executive order. FDA is the expert Federal agency charged by Congress with ensuring that food labeling is truthful and not misleading. Under section 403(a)(1) of the act, a food is deemed misbranded if its labeling is false or misleading in any particular. In determining whether labeling is misleading, FDA takes into account not only representations made or suggested by statement, word, design, device, or any combination thereof, but also the extent to which the labeling fails to reveal facts material in the light of such representations or material with respect to consequences which may result from the use of the article to which the labeling relates under the conditions of use prescribe in the labeling thereof or under such conditions of use as are customary or usual (section 201(n) of the act). In section 206 of FALCPA, Congress directs FDA to issue a proposed rule to define and permit use of the term “gluten-free” on the labeling of foods, in consultation with appropriate experts and stakeholders. As discussed elsewhere in this preamble, FDA has consulted with numerous experts and stakeholders in the development of this proposed rule. FDA has learned that different manufacturers currently have different and inconsistent definitions of the term “gluten-free,” and that individuals with celiac disease need a standardized definition of the term “gluten-free” to help them make purchasing decisions that will support their need to avoid consumption of gluten. Therefore, FDA believes that establishing a definition of the term “gluten-free” and uniform conditions for its use in the labeling of foods is needed to ensure that individuals with celiac disease are not misled and are provided with truthful and accurate information with respect to foods so labeled. If State authorities were permitted to impose labeling requirements that are inconsistent with those proposed in this rule, the federal objective of standardizing use of the term “gluten-free” in the labeling of foods to ensure that such labeling is neither false nor misleading would be frustrated. Section 4(c) of Executive Order 13132 instructs us to restrict any Federal preemption of State law to the “minimum level necessary to achieve the objectives of the statute pursuant to which the regulations are promulgated.'' This proposed rule would meet the preceding requirement because it would preempt state law only to the extent required to preserve Federal interests. Section 4(d) of Executive Order 13132 states that when an agency foresees the possibility of a conflict between State law and federally protected interests within the agency's area of regulatory responsibility, the agency “shall consult, to the extent practicable, with appropriate State and local officials in an effort to avoid such a conflict.'' Section 4(e) of the Executive order provides that “when an agency proposes to act through adjudication or rulemaking to preempt State law, the agency shall provide all affected State and local officials notice and an opportunity for appropriate participation in the proceedings.” FDA's Division of Federal and State Relations intends to invite the States' participation in this rulemaking by providing notice via fax and e-mail transmission to State health commissioners, State agriculture commissioners, and food program directors as well as FDA field personnel of FDA's publication of this proposed rule. The notice would provide the States with further opportunity for input on the rule. It would advise the States of FDA's possible action and encourage the States and local governments to review the notice and to provide any comments to the FDA Docket Number 2005N-0279, opened in the [enter date] **Federal Register** by [enter date]. FDA is providing an opportunity for State and local officials to comment on this proposed rule. The agency intends to comply with all of the applicable requirements under Executive Order 13132 to ensure that this proposed rule is consistent with the Executive order. FDA's Division of Federal-State Relations intends to invite the States' participation in this rulemaking by providing notice via fax and e-mail transmission to State health commissioners, State agriculture commissioners, and food program directors as well as FDA field personnel of FDA's publication of this proposed rule. The notice would provide the States with further opportunity for input on the rule. It would advise the States of FDA's possible action and encourage the States and local governments to review the proposed rule and to provide any comments to the FDA Docket No. 2005N-0279, opened in the July 19, 2005, **Federal Register** , by April 23, 2007. FDA is providing an opportunity for State and local officials to comment on this proposed rule. VII. Environmental Impact Analysis FDA has tentatively determined under 21 CFR 25.30(k) that this action is of a type that does not individually or cumulatively have a significant effect on the human environment. Therefore, neither an environmental assessment nor an environmental impact statement is required. VIII. Paperwork Reduction Act of 1995 FDA has tentatively concluded that this proposed rule contains no collection of information. Therefore, clearance by the Office of Management and Budget under the Paperwork Reduction Act of 1995 is not required. IX. Comments Interested persons may submit to the Division of Dockets Management (see ADDRESSES ) written or electronic comments regarding this document. Submit a single copy of electronic comments or two paper copies of any mailed comments, except that individuals may submit one paper copy. Comments are to be identified by Docket No. 2005N-0279. If you base your comments on scientific evidence or data, please submit copies of the specific information along with your comments. Received comments may be seen in the Division of Dockets Management between 9 a.m. and 4 p.m., Monday through Friday. X. References The following references have been placed on display in the Division of Dockets Management (see ADDRESSES ) and may be seen by interested persons between 9 a.m. and 4 p.m., Monday through Friday. FDA has verified the cited Web site addresses, but is not responsible for subsequent changes to them after this document publishes in the **Federal Register** . 1. National Institutes of Health (NIH), NIH Consensus Development Conference on Celiac Disease, “National Institutes of Health Consensus Development Conference Statement,” NIH, Bethesda, MD, pp. 1-15, June 28-30, 2004, accessible at *http://consensus.nih.gov/2004/2004CeliacDisease118html.htm* on June 22, 2006. 2. Shan, L., O. Molberg, I. Parrot, et al., “Structural Basis for Gluten Intolerance in Celiac Sprue,” *Science* , 297:2275-2279, 2002. 3. Jabri, B., D.D. Kasarda, and H.R Green, “Innate and Adaptive Immunity: The Yin and Yang of Celiac Disease,” *Immunological Reviews* , 206:219-231, 2005. 4. National Digestive Disease Information Clearinghouse, National Institute of Diabetes and Digestive and Kidney Diseases, National Institutes of Health (NIH), “Celiac Disease,” NIH Publication No. 06-4269, pp. 1-11. October 2005, accessible at *http://digestive.niddk.nih.gov/ddiseases/pubs/celiac/* on June 22, 2006. 5. Dewar, D., S.P. Pereira, and P.J. Ciclitira, “The Pathogenesis of Coeliac Disease,” *International Journal of Biochemistry & Cell Biology* , 36:17-24, 2004. 6. Fasano, A. and C. Catassi, “Current Approaches to Diagnosis and Treatment of Celiac Disease: An Evolving Spectrum,” *Gastroenterology* , 120(3):636-651, 2001. 7. Farrell, R.J. and C.P. Kelly, “Celiac Sprue,” *New England Journal of Medicine* , 346(3):180-188, 2002. 8. Mäki, M. and P. Collin, “Coeliac Disease,” *Lancet* , 349:1755-1759, 1997. 9. Fasano, A., “Celiac Disease—How to Handle a Clinical Chameleon,” *New England Journal of Medicine* , 348:2568-2570, 2003. 10. Catassi, C. and A. Fasano, “Celiac Disease as a Cause of Growth Retardation in Childhood,” *Current Opinion in Pediatrics* , 16:445-449, 2004. 11. Catassi, C., E. Fabiani, G. Corrao, et al., “Risk of Non-Hodgkin Lymphoma in Celiac Disease,” *Journal of the American Medical Association* , 287(11):1413-1419, 2002. 12. Peters, U., J. Askling, G. Gridley, et al., “Causes of Death in Patients With Celiac Disease in a Population-Based Swedish Cohort, “ *Archives of Internal Medicine* , 163:1566-1572, 2003. 13. Green, P.H.R. and B. Jabri, “Coeliac Disease,” *Lancet* , 362:383-391, 2003. 14. Pietrzak, M.M., C. Catassi, S. Drago, et al., “Celiac Disease: Going Against the Grains,” *Nutrition in Clinical Practice* , 16:335-344, December 2001. 15. Corrao, G., G.R. Corazza, V. Bagnardi, et al., “Mortality in Patients With Coeliac Disease and Their Relatives: A Cohort Study,” *Lancet* , 358:356-361, 2001. 16. Rostom, A., C. Dubé, A. Cranney, et al., “Celiac Disease,” Evidence Report/Technology Assessment Number 104, Prepared by the University of Ottawa Evidence-Based Practice Center Under Contract No. 290-02-0021 for the Agency for Healthcare Research and Quality (AHRQ), U.S. Department of Health and Human Services, Rockville, MD, AHRQ Publication No. 04-E029-2, p. 140, September 2004. 17. Hamilton, F., “Celiac Disease-A Not So Uncommon Disorder,” Presentation, Transcript of the Center for Food Safety and Applied Nutrition, Food and Drug Administration Public Meeting on Gluten-Free Food Labeling held in College Park, MD, p. 33, August 19, 2005, accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279-tr00001-01-vol16.doc* on June 22, 2006. (Also see errata sheet for transcript accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279-tr00001-02-erratta-vol16.doc* on June 22, 2006.) 18. Peterson, T., “Goodbye to Gluten,” *The Salt Lake Tribune* , September 12, 2005. 19. Sanders, D.S., M.J. Carter, D.P. Hurlstone, et al., “Association of Adult Coeliac Disease With Irritable Bowel Syndrome: A Case-Control Study in Patients Fulfilling ROME II Criteria Referred to Secondary Care,” *Lancet* , 358:1504-1508, 2001. 20. Brown, A., *Understanding Food Principles and Preparation* , Second Ed., Wadsworth/Thomson Learning, Belmont, CA, pp. 402-403 and 420-421, 2004. 21. Pomeranz, Y., *Modern Cereal Science and Technology* , VCH Publishers, Inc., New York, NY, pp. 40-42, 44, and 53, 1987. 22. Skerritt, J.H. and A.S. Hill, “Enzyme Immunoassay for Determination of Gluten in Foods: Collaborative Study,” *Journal of the Association of Official Analytical Chemists* , 74(2):257-264, 1991. 23. Hischenhuber, C., R. Crevel, B. Jarry, et al., “Review Article: Safe Amounts of Gluten for Patients With Wheat Allergy or Coeliac Disease,” *Alimentary Pharmacology & Therapeutics* , 23(5):559-575, March 1, 2006. 24. Shewry, P.R., N.G. Halford, P.S Belton, et al., “The Structure and Properties of Gluten: An Elastic Protein From Wheat Grain,” *Philosophical Transactions of the Royal Society of London. Series B, Biological Sciences* , 357:133-142, 2002. 25. Kasarda, D.D., Personal Communication, January 22, 2005. 26. Dicke, W.K., H.A. Weijers, and J.H van de Kamer, “Coeliac Disease. II. The Presence in Wheat of a Factor Having a Deleterious Effect in Cases of Coeliac Disease,” *Acta Paediatricia* , 42:34-42, January 1953. 27. van de Kamer, J.H., H.A. Weijers, and W.K. Dicke, “Coeliac Disease. IV. An Investigation Into the Injurious Constituents of Wheat in Connection With Their Action on Patients With Coeliac Disease,” *Acta Paediatrica* , 42:223-231, May 1953. 28. Baker, P.G. and A.E. Read, “Oats and Barley Toxicity in Coeliac Patients,” *Postgraduate Medical Journal* , 52:264-268, May 1976. 29. Anand, B.S., J. Piris, and S.C. Truelove, “The Role of Various Cereals in Coeliac Disease,” *Quarterly Journal of Medicine* , New Series 47(185):101-110, 1978. 30. Kasarda, D.D., “What We Know About Grain Safety,” Paper Presented at the Columbia University Celiac Disease and Other Food Intolerances Conference, Columbia University Medical Center, New York, NY, Program Description & Objectives, pp. 23-33, October 22, 2004. 31. Kasarda, D.D., “Grains in Relation to Celiac Disease,” *Cereal Foods World* , 46(5):209-210, 2001. 32. Arentz-Hansen, H., B. Fleckenstein, O. Molberg, et al., “The Molecular Basis for Oat Intolerance in Patients With Celiac Disease,” *PLoS Medicine* , 1:84-92, October 2004. 33. Johnson, D.L., D. Sands, and A. Pilgeram, “Indian Ricegrass: A Gluten-Free Cereal,” Presentation Abstract, The Association for the Advancement of Industrial Crops Annual Meeting, Saskatoon, Saskatchewan, Canada, Program and Abstracts, p. 16, August 25-28, 2002, accessible at *http://www.aaic.org/02progrm.htm* on June 22, 2006. 34. Kupper, C., “Dietary Guidelines for Celiac Disease and Implementation,” Presentation Abstract, National Institutes of Health (NIH), NIH Consensus Development Conference on Celiac Disease, Bethesda, MD, pp. 91-95, June 28-30, 2004, accessible at *http://consensus.nih.gov/2004/2004CeliacDisease118Program.pdf* on June 22, 2006. 35. van de Wal, Y., Y.M.C. Kooy, P. van Veelen, et al., “Glutenin Is Involved in the Gluten-Driven Mucosal T Cell Response,” *European Journal of Immunology* , 29(10):3133-3139, 1999. 36. Vader, W., Y. Kooy, P. van Veelen, et al., “The Gluten Response in Children With Celiac Disease is Directed Toward Multiple Gliadin and Glutenin Peptides,” *Gastroenterology* ,122(7):1729-1737, 2002. 37. Molberg, O., N.S. Flaete, T. Jensen, et al., “Intestinal T-Cell Responses to High-Molecular-Weight Glutenins in Celiac Disease,” *Gastroenterology* , 125(2):337-344, 2003. 38. Ciclitira, P.J., D.J. Evans, N.L.K. Fagg, et al., “Clinical Testing of Gliadin Fractions in Coeliac Patients,” *Clinical Science* , 66:357-364, 1984. 39. Ellis, H.J., E.L. Pollock, W. Engel, et al., “Investigation of the Putative Immunodominant T Cell Epitopes in Coeliac Disease,” *Gut* , 52:212-217, 2003. 40. European Food Safety Agency (EFSA), “Opinion of the Scientific Panel on Dietetic Products, Nutrition and Allergies on a Request from the Commission Relating to the Evaluation of Allergenic Foods for Labelling Purposes,” EFSA-Q-2003-016, *EFSA Journal* , 32:40-45, 146, 147, 152, 155-157, 159, 160, 167, 169, 171, 174, 181, 187, 189, 192, 193, and 195, 2004, accessible at *http://www.efsa.europa.eu./en/science/nda/nda_opinions/341.html* on June 27, 2006. 41. Thompson, T., “Wheat Starch, Gliadin, and the Gluten-Free Diet,” *Journal of the American Dietetic Association* , 101(12):1456-1459, December 2001. 42. Kagnoff, M.F., “Overview and Pathogenesis of Celiac Disease,” *Gastroenterology* , 128:S10-S18, April Supplement, 2005. 43. Kasarda, D.D., “Celiac Disease and Safe Grains,” Web page, July 2003, accessible at *http://wheat.pw.usda.gov/ggpages/topics/Celiac.vs.grains.html* on June 22, 2006. 44. Thompson, T., “Oats and the Gluten-Free Diet,” *Journal of the American Dietetic Association* , 103(3):376-379, March 2003. 45. Lundin, K.E.A., E.M. Nilsen, H.G. Scott, et al., “Oats Induced Villous Atrophy in Coeliac Disease,” *Gut* , 52(11):1649-1652, 2003. 46. Janatuinen, E.K., P.H. Pikkarainen, T.A. Kemppainen, et al., “A Comparison of Diets With and Without Oats in Adults With Celiac Disease,” *New England Journal of Medicine* , 333(16):1033-1037, 1995. 47. Hardman, C.M., J.J. Garioch, J.N. Leonard, et al., “Absence of Toxicity of Oats in Patients With Dermatitis Herpetiformis,” *New England Journal of Medicine* , 337(26):1884-1887, 1997. 48. Janatuinen, E.K., T.A. Kemppainen, P.H. Pikkarainen, et al., “Lack of Cellular and Humoral Immunological Responses to Oats in Adults With Coeliac Disease,” *Gut* , 46(3):327-331, 2000. 49. Janatuinen, E.K., T.A. Kemppainen, R.J. Julkunen, et al., “No Harm From Five Year Ingestion of Oats in Coeliac Disease,” *Gut* , 50(3):332-335, 2002. 50. Högberg, L., P. Laurin, K. Faith-Magnusson, K., et al., “Oats to Children With Newly Diagnosed Celiac Disease: A Randomized Double Blind Study,” *Gut* , 53:649-654, 2004. 51. Peräaho, M., P. Collin, K. Kaukinen, et al., “Oats Can Diversify a Gluten-Free Diet in Celiac Disease and Dermatitis Herpetiformis,” *Journal of the American Dietetic Association* , 104(7):1148-1150, July 2004. 52. Kelly, C., Public comment number EC4 submitted on July 28, 2005 to Docket No. 2005N-0231 pertaining to Center for Food Safety and Applied Nutrition, Food and Drug Administration Draft Report entitled “Approaches to Establish Thresholds for Major Food Allergens and for Gluten in Food,” pp. 1-2, June 2005, accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0231/05N-0231-EC4.htm* on June 22, 2006. 53. Kasarda, D.D., Agricultural Research Service, Western Regional Research Center, U.S. Department of Agriculture, “Grains in Relation to Celiac (Coeliac) Disease,” Web page, updated 1999, accessible at *http://wheat.pw.usda.gov/ggpages/topics/celiac.html* on June 22, 2006. 54. Cureton, P., “Celiac Consumer: Survey Results,” Presentation and Remarks During Question and Answer Period, Transcript of the Center for Food Safety and Applied Nutrition, Food and Drug Administration Public Meeting on Gluten-Free Food Labeling held in College Park, MD, pp. 214-215 and 236-237, August 19, 2005, accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279-tr00001-01-vol16.doc* on June 22, 2006.. (Also see errata sheet for transcript accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279-tr00001-02-erratta-vol16.doc* on June 22, 2006.) 55. Lee, A., Remarks During Question and Answer Period, Transcript of the Center for Food Safety and Applied Nutrition, Food and Drug Administration Public Meeting on Gluten-Free Food Labeling held in College Park, MD, pp. 237-238, August 19, 2005, accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279-tr00001-01-vol16.doc* on June 22, 2006. (Also see errata sheet for transcript accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279-tr00001-02-erratta-vol16.doc* on June 22, 2006.) 56. Case, S., *Gluten-Free Diet: A Comprehensive Guide, Expanded Edition* , Case Nutrition Consulting, Regina, Saskatchewan, Canada, pp. 21-24, 28, and 29, 2006. 57. Thompson, T., “Questionable Foods and the Gluten-Free Diet,” *Journal of the American Dietetic Association* , 100(4):463-465, April 2000. 58. American Dietetic Association (ADA), “Celiac Disease-Nutrition Care-Grains to Avoid,” *ADA Nutrition Care Manual* ©, American Dietetic Association, Chicago, Illinois, 1 electronic page, 2006, accessible at *www.nutritioncaremanual.org* on June 26, 2006. 59. American Dietetic Association (ADA), “Celiac Disease-Nutrition Care-Oats,” *ADA Nutrition Care Manual* ©, American Dietetic Association, Chicago, Illinois, 2 electronic pages, 2006, accessible at *www.nutritioncaremanual.org* on June 26, 2006. 60. Hager, M., American Dietetic Association, Public comment letter EC-1482 submitted on September 20, 2005, to Docket No. 2005N-0279 pertaining to the Center for Food Safety and Applied Nutrition, Food and Drug Administration Public Meeting on Gluten-Free Food Labeling held in College Park, MD, pp. 1-3, August 19, 2005, accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279-EC1482-Attach-1.pdf* on June 22, 2006. 61. U.S. Department of Agriculture, “Official United States Standards for Grain, Subpart A-General Provisions,” pp. A1-A5, June 1999, accessible at *http://151.121.3.117/reference-library/standards/810101.pdf* on June 2005. [Note standards for specific grains are accessible at *http://www.gipsa.usda.gov/GIPSA/webapp?area=home&subject=grpi&topic=sq-ous* on June 22, 2006.] 62. American Gastroenterological Association, “Medical Position Statement: Celiac Sprue,” *Gastroenterology* , 120:1522-1525, 2001. 63. Thompson, T., “Gluten Contamination of Commercial Oat Products in the Unites States,” *New England Journal of Medicine* , 351(19):2021-2022, 2004. 64. Hernando A., J.R. Mujico, D. Juanas, et al., “Confirmation of the Cereal Type in Oat Products Highly Contaminated With Gluten,” *Journal of the American Dietetic Association* , 106(5):665, May 2006. 65. Armour, B. and T.B. Perry, Cream Hill Estates Ltd., Public comment letter EMC299 submitted on November 19, 2005, to Docket No. 2005N-0279 pertaining to the Center for Food Safety and Applied Nutrition, Food and Drug Administration Public Meeting on Gluten-Free Food Labeling held in College Park, MD, pp. 1-3, August 19, 2005, accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279_emc-000299-03.pdf* on June 22, 2006. 66. Smith, S., Gluten Free Oats LLC, Public comment letter EMC301 submitted on March 20, 2006 to Docket No. 2005N-0279 pertaining to the Center for Food Safety and Applied Nutrition, Food and Drug Administration Public Meeting on Gluten-Free Food held in College Park, MD, pp. 1-2, August 19, 2005. 67. The Threshold Working Group, “Approaches to Establish Thresholds for Major Food Allergens and for Gluten in Food,” Draft Report, Center for Food Safety and Applied Nutrition, Food and Drug Administration, College Park, MD, pp. 1-103, June 2005, accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0231/05n-0231-rpt0001.pdf* and *http://www.cfsan.fda.gov/~dms/alrgn.html* on June 22, 2006. 68. Food and Drug Administration, “FDA's Responses to Public Comments on the Draft Report ‘Approaches to Establish Thresholds for Major Food Allergens and for Gluten in Food,’” Web site posting, March 2006, accessible at *http://www.cfsan.fda.gov/~dms/alrgcom.html* on June 22, 2006. 69. The Threshold Working Group, “Approaches to Establish Thresholds for Major Food Allergens and for Gluten in Food,” Revised Report, Center for Food Safety and Applied Nutrition, Food and Drug Administration, College Park, MD, pp. 1-106, March 2006, accessible at *http://www.cfsan.fda.gov/~dms/alrgn2.html* on June 22, 2006. 70. Food Advisory Committee, Center for Food Safety and Applied Nutrition, Food and Drug Administration, “Summary Minutes for the Food Advisory Committee Meeting on ‘Advice on CFSAN's Draft Report: Approaches to Establish Thresholds for Major Food Allergens and for Gluten in Food,’” Greenbelt, MD, pp. 1-11, July 13-15, 2005, accessible at *http://www.fda.gov/ohrms/dockets/ac/05/minutes/2005-4160m1_summary%20minutes.pdf* and *http://www.fda.gov/ohrms/dockets/ac/cfsan05.html* on June 22, 2006. 71. Størsrud, S., L.R. Hulthén, and R.A. Lenner, et al., “Beneficial Effects of Oats in the Gluten-Free Diet of Adults With Special Reference to Nutrient Status, Symptoms and Subjective Experiences,” *British Journal of Nutrition* , 90:101-107, 2003. 72. Burke, S.J., S.J. Milberg, and W.W. Moe, “Displaying Common but Previously Neglected Health Claims on Product Labels: Understanding Competitive Advantages, Deception, and Education,” *Journal of Public Policy & Marketing* , 16(2):242-255, Fall 1997. 73. Gendel, S.M., Memorandum to the Administrative Record for the Gluten-Free Food Labeling Proposed Rule, pp. 1-5 (with 31 attachments), May 12, 2006. 74. Méndez, E., V. Carmen, U. Immer, et al., “Report of a Collaborative Trial to Investigate the Performance of the R5 Enzyme Linked Immunoassay to Determine Gliadin in Gluten-Free Food,” *European Journal of Gastroenterology & Hepatology* , 17(10):1053-1063, 2005. 75. Johnson, K., Personal Communication, March 16, 2006. 76. Matsuda, R., Y. Yoshioka, H. Akiyama, et al., “Interlaboratory Evaluation of Two Enzyme-Linked Immunosorbent Assay Kits for the Detection of Egg, Milk, Wheat, Buckwheat, and Peanut in Foods,” *Journal of AOAC INTERNATIONAL* , 89(6):1600-1608, November/December 2006. 77. AOAC INTERNATIONAL, Official Method 991.19: “Gliadin as a Measure of Gluten in Foods.” Chapter 32, Cereal Foods, *Official Methods of Analysis of AOAC INTERNATIONAL* , 18th Ed., AOAC INTERNATIONAL, Gaithersburg, MD, pp. 15-17, 2005. 78. Fielder, R., Personal Communication, May 10, 2006. 79. Food Standards Australian New Zealand, “Australian New Zealand Food Standards Code: Chapter 1—General Food Standards, Part 1.2—Labelling and Other Information Requirements, Standard 1.2.8—Nutrition Information Requirements,” pp. 1 and 16-17, 2006, accessible at *http://www.foodstandards.gov.au/foodstandardscode* June 27, 2006. 80. Fasano, A., Personal Communication, November 22, 2004. 81. Catassi, C., E. Fabiani, G. Iacono, et al., “Toxicity of Gluten Traces in Patients on Treatment for Celiac Disease. Results of a Prospective, Placebo-Controlled, Double-Blind, Randomized Study,” Presentation Abstract No. S1775, *Digestive Disease Week* , May 14-19, 2005, accessible at *http://precis.preciscentral.com/files/source/67/html/45832.htm* on June 22, 2006. 82. Collin, P., L. Thorell, K. Kaukinen, et al., “The Safe Threshold for Gluten Contamination in Gluten-Free Products. Can Trace Amounts Be Accepted in the Treatment of Coeliac Disease?” *Alimentary Pharmacology & Therapeutics* , 19(12):1277-1283, June 2004. 83. Chartrand, L.J., P.A. Russo, A.G, DuHaime, et al., “Wheat Starch Intolerance in Patients With Celiac Disease,” * Journal of the American Dietetic Association * , 97(6):612-618, June 1997. 84. Fasano, A., I. Berti, T. Gerarduzzi, et al., “Prevalence of Celiac Disease in At-Risk and Not-At-Risk Groups in the United States. A Large Multicenter Study,” *Archives of Internal Medicine* , 163:286-292, 2003. 85. U.S. Census Bureau, Population Division, “U.S. POPClock Projection,” Web page, accessible at *http://www.census.gov/population/www/popclockus.html* on August 18, 2005 86. Blast, A., National Foundation for Celiac Awareness, Public Statement, Transcript of the Center for Food Safety and Applied Nutrition, Food and Drug Administration Public Meeting on Gluten-Free Food Labeling held in College Park, MD, p. 287, August 19, 2005, accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279-tr00001-01-vol16.doc* June 22, 2006. (Also see errata sheet for transcript accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279-tr00001-02-erratta-vol16.doc* June 22, 2006.) 87. Schluckebier, M., “Food Labeling Concerns for CD/DH,” Presentation, Transcript of the Center for Food Safety and Applied Nutrition, Food and Drug Administration Public Meeting on Gluten-Free Food Labeling held in College Park, MD, p. 200, August 19, 2005, accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279-tr00001-01-vol16.doc* on June 22, 2006. (Also see errata sheet for transcript accessible at *http://www.fda.gov/ohrms/dockets/dockets/05n0279/05n-0279-tr00001-02-erratta-vol16.doc* on June 22, 2006.) 88. Bureau of Labor Statistics, U.S. Department of Labor (USDL), “Employer Costs for Employee Compensation Summary,” USDL: 05-2279, December 9, 2005. 89. Kaukinen, K., P. Collin, K. Holm, et al., “Wheat Starch-Containing Gluten-Free Flour Products in the Treatment of Coeliac Disease and Dermatitis Herpetiformis. A Long Term Follow-Up Study,” *Scandinavian Journal of Gastroenterology* , 34:163-169, 1999. 90. McCrae, W.M., M.A. Eastwood, M.R. Martin, et al., “Neglected Coeliac Disease,” *Lancet* , 1:187-190, 1975. 91. Sdepanian V.L., I.C.A. Scaletsky, U. Fagundes-Neto, et al., “Assessment of Gliadin in Supposedly Gluten-Free Foods Prepared and Purchased by Celiac Patients,” *Journal of Pediatric Gastroenterology and Nutrition* , 32:65-70, January 2001. 92. Codex Alimentarius Commission, Food and Agriculture Organization
(FAO)of the United Nations, World Health Organization (WHO), Joint FAO/WHO Food Standards Programme, Codex Committee on Nutrition and Foods for Special Dietary Uses, Twenty-fifth Session, “Proposed Draft Revised Standard for Gluten-Free Food *At Step 7* ,” Comments from Sweden, Finland, AOECS-Association of European Coeliac Societies, IWGA-International Wheat Gluten Association, CX/NFSDU 03/4-Add. 1, pp. 1-11, October 2003. 93. Lohiniemi, S., M. Mäki, K. Kaukinene, et al., “Gastrointestinal Symptoms Rating Scale in Coeliac Disease Patients on Wheat Starch-Based Gluten-Free Diets,” *Scandinavian Journal of Gastroenterology* , September, 35(9):947-949, October 2000. 94. Peräaho, M., K. Kaukinen, K. Paasikivi, et al., “Wheat-Starch-Based Gluten-Free Products in the Treatment of Newly Detected Coeliac Disease: Prospective and Randomized Study,” *Alimentary Pharmacology & Therapeutics* , 17(4):587-594, February 2003. 95. Faulkner-Hogg, K.B., W.S. Selby, and R.H. Loblay, “Dietary Analysis in Symptomatic Patients With Coeliac Disease on a Gluten-Free Diet: The Role of Trace Amounts of Gluten and Non-Gluten Products,” *Scandinavian Journal of Gastroenterology* , 34(38):784-789, August 1999. List of Subjects in 21 CFR Part 101 Food labeling, Nutrition, Reporting and recordkeeping requirements. For the reasons discussed in the preamble, the Food and Drug Administration proposes to amend 21 CFR part 101 as follows: PART 101—FOOD LABELING 1. The authority citation for 21 CFR part 101 continues to read as follows: Authority: 15 U.S.C. 1453, 1454, 1455; 21 U.S.C. 321, 331, 342, 343, 348, 371; 42 U.S.C. 243, 264, 271. 2. Section 101.91 is added to subpart F to read as follows: § 101.91 Gluten-free labeling of food.
(a)*Definitions* .
(1)The term “prohibited grain” means any one of the following grains or their crossbred hybrids (e.g., triticale, which is a cross between wheat and rye):
(i)Wheat, including any species belonging to the genus *Triticum* ;
(ii)Rye, including any species belonging to the genus *Secale* ; or
(iii)Barley, including any species belonging to the genus *Hordeum* .
(2)The term “gluten” means the proteins that naturally occur in a prohibited grain and that may cause adverse health effects in persons with celiac disease (e.g., prolamins and glutelins).
(3)The labeling claim “gluten-free” or similar claim (e.g., “free of gluten,” “without gluten,” “no gluten”) means that the food bearing the claim in its labeling does not contain any of the following:
(i)An ingredient that is a prohibited grain (e.g., spelt wheat);
(ii)An ingredient that is derived from a prohibited grain and that has not been processed to remove gluten (e.g., wheat flour);
(iii)An ingredient that is derived from a prohibited grain and that has been processed to remove gluten (e.g., wheat starch), if the use of that ingredient results in the presence of 20 parts per million
(ppm)or more gluten in the food (i.e., 20 micrograms or more gluten per gram of food);
(iv)20 ppm or more gluten.
(b)*Requirements* .
(1)A food that bears the claim “gluten-free” or similar claim in its labeling and fails to meet the conditions specified in paragraph (a)(3) of this section will be deemed misbranded.
(2)With the exception of foods made from oats, a food that does not inherently contain any gluten from a prohibited grain (e.g., milk, corn, frozen concentrated orange juice) and that bears the claim “gluten-free” in its labeling will be deemed misbranded unless:
(i)The claim refers to all foods of that same type (e.g., “milk, a gluten-free food,” “all milk is gluten-free”); and
(ii)The food does not contain 20 ppm or more gluten.
(3)A food made from oats that bears the claim “gluten-free” or similar claim in its labeling will be deemed misbranded if the claim refers to all foods of the same type (e.g., “all oats are gluten-free”) or if the food contains 20 ppm or more gluten.
(c)*Compliance* . When compliance with paragraph
(b)of this section is based on an analysis of the food, FDA will use a method that can reliably detect the presence of 20 ppm gluten in a variety of food matrices, including both raw and cooked or baked products. Dated: January 16, 2007. Jeffrey Shuren, Assistant Commissioner for Policy. [FR Doc. E7-843 Filed 1-22-07; 8:45 am] BILLING CODE 4160-01-S DEPARTMENT OF JUSTICE Federal Bureau of Investigation 28 CFR Part 20 [Docket No. FBI 113; AG Order No. 2855-2007] RIN 1110-AA24 Carriage of Concealed Weapons Pursuant to Public Law 108-277; the Law Enforcement Officers Safety Act of 2003 AGENCY: Federal Bureau of Investigation (FBI), Department of Justice. ACTION: Notice of proposed rulemaking with request for comments. SUMMARY: The Department of Justice (the Department) is amending Title 28 of the Code of Federal Regulations to authorize access to FBI-maintained criminal justice information systems for the conduct of background checks for the purpose of issuing identification documents to retired law enforcement officers. DATES: Written comments must be received on or before March 26, 2007. ADDRESSES: All comments may be submitted to Assistant General Counsel Harold M. Sklar, Federal Bureau of Investigation, CJIS Division, 1000 Custer Hollow Road, Module E-3, Clarksburg, West Virginia, 26306, or by telefacsimile to
(304)625-3944. To ensure proper handling, please reference FBI Docket No. 113 on your correspondence. You may view an electronic version of this proposed rule at *www.regulations.gov* . You may also comment via electronic mail at *enexreg@leo.gov* or by using the *www.regulations.gov* comment form for this regulation. When submitting comments electronically you must include FBI Docket No. [2855-2007] in the subject box. FOR FURTHER INFORMATION CONTACT: Assistant General Counsel Harold M. Sklar, telephone number
(304)625-2000. SUPPLEMENTARY INFORMATION: Background The Department is amending part 20 of Title 28, “Criminal Justice Information Systems,” to authorize criminal justice agencies to access FBI criminal history record information appearing in the National Crime Information Center
(NCIC)Interstate Identification Index
(III)and the Fingerprint Identification Record System
(FIRS)to support implementation of Public Law 108-277. On July 22, 2004, the Law Enforcement Officers Safety Act of 2003 (Pub. L. 108-277) became law. Public Law 108-277 amended Title 18, United States Code, to exempt “qualified” current and retired law enforcement officers
(LEOs)from State laws prohibiting the carrying of concealed firearms (except when state law restricts the possession of concealed firearms on public property or permits private property owners to restrict the possession of concealed firearms on their property). Under the new 18 U.S.C. 926C(d), retired LEOs seeking to exercise this privilege are required to possess photographic identification issued by the criminal justice agency
(CJA)from which they retired from service. On January 31, 2005, the Attorney General issued guidance on Public Law 108-277 mandating that Department of Justice
(DOJ)Criminal Justice Components issue photographic identification (ID cards) to its eligible retired LEOs that identify their status as “retired law enforcement officers” and provide the date of retirement. Additionally, various CJAs have asked the FBI whether they may access the III database to screen their retired LEOs prior to issuing ID cards under the Act. Section 534 of title 28, United States Code, generally permits the dissemination of III and FIRS information to CJAs for “official use.” Section 534 is implemented in this regard by 28 CFR part 20. Since 1974, access to and dissemination of III information under part 20 has been largely restricted to “criminal justice agencies for criminal justice purposes, which purposes include the screening of employees or applicants for employment hired by criminal justice agencies * * *.” 28 CFR 20.33(a)(1). Although the term “criminal justice purpose” referenced in § 20.33(a)(1) is not specifically defined in the regulations, it has traditionally been considered to include activities within the definition of “administration of criminal justice” in § 20.3(b): “performance of any of the following activities: Detection, apprehension, detention, pretrial release, post-trial release, prosecution, adjudication, correctional supervision, or rehabilitation of accused persons or criminal offenders.” Taken together, these regulations currently do not clearly support access to III and FIRS for the purpose of issuing identification documents for retired LEOs. As a result, the FBI sought and obtained the concurrence of the Criminal Justice Information Services Advisory Policy Board (CJIS APB) (a body created pursuant to the Federal Advisory Committee Act, § 2, 5 U.S.C. App. 2) to amend the definition of “administration of criminal justice” to include background checks conducted for the purpose of issuing identification documents to retired LEOs pursuant to section 926C(d) of Public Law 108-277. To provide regulatory consistency, we also propose to relocate the reference in § 20.33(a)(1) to “the screening of employees or applicants for employment hired by criminal justice agencies” to the definition of “administration of criminal justice” appearing at § 20.3(b). We are also making clear in section 20.3(b) that the term “criminal justice purpose” includes activities defined as the “administration of criminal justice.” This amendment will expressly authorize access to the III and the FIRS by Federal, state, and local CJAs for the purpose of issuing identification documents to eligible retired LEOs pursuant to Public Law 108-277. Further, inasmuch as the definitions appearing in 28 CFR 20.3 apply to both 28 CFR subparts B and C, this change resolves any ambiguity about the existing authority to access state criminal justice systems (in the absence of contrary state authority) to screen CJA applicants and employees. Applicable Administrative Procedures and Executive Orders Executive Order 12866—Regulatory Planning and Review The proposed rule has been drafted and reviewed in accordance with Executive Order 12866, section 1(b), Principles of Regulation. The Department has determined that this rule is a significant regulatory action under section 3(f) of Executive Order 12866. Executive Order 13132—Federalism This rule will not have a substantial, direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, in accordance with Executive Order 13132, it is determined that this rule does not have sufficient federalism implications to warrant the preparation of a Federalism Assessment. Executive Order 12988—Civil Justice Reform The rule meets the applicable standards set forth in sections 3(a) and 3(b)(2) of Executive Order 12988. Regulatory Flexibility Act The Attorney General, in accordance with the Regulatory Flexibility Act (5 U.S.C. 601 et seq.), has reviewed this rule and, by approving it, certifies that this rule will not have a significant economic impact on a substantial number of small entities (5 U.S.C. 605(b)). This rule imposes minimal costs on businesses, organizations, or governmental jurisdictions (whether large or small). Unfunded Mandates Reform Act of 1995 This rule will not result in the expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year, and it will not significantly or uniquely affect small governments. Therefore, no actions were deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995. Small Business Regulatory Enforcement Fairness Act of 1996 This rule is not a “major rule” as defined by the Small Business Regulatory Enforcement Fairness Act of 1996, 5 U.S.C. 804(2). This proposed rule will not result in an annual effect on the economy of $100 million or more, a major increase in costs or prices, or have significant adverse effects on competition, employment, investment, productivity, innovation, or on the ability of United States-based companies to compete with foreign-based companies in domestic and export markets. Paperwork Reduction Act of 1995 The rule does not contain collection of information requirements. Therefore, clearance by the Office of Management and Budget under the Paperwork Reduction Act, 44 U.S.C. 3501 et seq., is not required. List of Subjects in 28 CFR Part 20 Classified information, Crime, Intergovernmental relations, Investigations, Law enforcement, Privacy. Accordingly, part 20 of title 28 of the Code of Federal Regulations is proposed to be amended as follows: PART 20—CRIMINAL JUSTICE INFORMATION SYSTEMS 1. The authority citation for part 20 continues to read as follows: Authority: 28 U.S.C. 534; Pub. L. 92-544, 86 Stat. 1115; 42 U.S.C. 3711, et seq.; Pub. L. 99-169, 99 Stat. 1002, 1008-1011, as amended by Pub. L. 99-569, 100 Stat. 3190, 3196; Pub. L. 101-410, 104 Stat. 890, as amended by Pub. L. 104-134, 110 Stat. 1321. 2. Section 20.3 is amended by revising paragraph
(b)to read as follows: § 20.3 Definitions. As used in these regulations:
(b)*Administration of criminal justice* means the performance of any of the following activities: Detection, apprehension, detention, pretrial release, post-trial release, prosecution, adjudication, correctional supervision, or rehabilitation of accused persons or criminal offenders. The term “criminal justice purpose” in 20 CFR 20.33(a)(1) includes activities defined as the “administration of criminal justice.” The administration of criminal justice also includes
(i)Criminal identification activities and the collection, storage, and dissemination of criminal history record information;
(ii)The screening of employees or applicants for employment hired by criminal justice agencies; and
(iii)The issuance of identification documents to current and retired law enforcement officers pursuant to Public Law 108-277. 3. Section § 20.33 is amended by revising paragraphs
(a)introductory text and (a)(1) to read as follows: § 20.33 Dissemination of criminal history record information.
(a)Criminal history record information contained in the III System and the FIRS may be made available:
(1)To criminal justice agencies for criminal justice purposes; Dated: January 2, 2007. Alberto R. Gonzales, Attorney General. [FR Doc. E7-150 Filed 1-22-07; 8:45 am] BILLING CODE 4410-02-P DEPARTMENT OF DEFENSE Office of the Secretary [DoD-2006-OS-0033; 0790-AI10] 32 CFR Part 311 Office of the Secretary Privacy Program AGENCY: Department of Defense. ACTION: Proposed rule. SUMMARY: This rule proposed updates and implements policies and procedures for the Privacy Act Program in the Office of the Secretary of Defense and organizations provided administrative support by the Washington Headquarters Services. DATES: Comments must be received by March 26, 2007. ADDRESSES: You may submit comments, identified by docket number and or RIN number and title, by any of the following methods: • *Federal eRulemaking Portal:* *http://www.regulations.gov.* Follow the instructions for submitting comments. • *Mail:* Federal Docket Management System Office, 1160 Defense Pentagon, Washington, DC 20301-1160. *Instructions:* All submissions received must include the agency name and docket number or Regulatory Information Number
(RIN)for this **Federal Register** document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at *http://regulations.gov* as they are received without change, including any personal identifiers or contact information. FOR FURTHER INFORMATION CONTACT: Ms. J. Irvin, 703-696-4940. SUPPLEMENTARY INFORMATION: Executive Order 12866, “Regulatory Planning and Review” It has been determined that 32 CFR part 311 is not a significant regulatory action. The rule does not:
(1)Have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a section of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or tribal governments or communities;
(2)Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency;
(3)Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or
(4)Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in this Executive Order. Unfunded Mandates Reform Act (Sec. 202, Pub. L. 104-4) It has been certified that this rule does not contain a Federal mandate that may result in the expenditure by State, local and tribal governments, in aggregate, or by the private sector, of $100 million or more in any one year. Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. 601) It has been certified that this rule is not subject to the Regulatory Flexibility Act (5 U.S.C. 601) because it would not, if promulgated, have a significant economic impact on a substantial number of small entities. Certification is required. Public Law 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35) It has been certified that this rule does impose reporting or recordkeeping requirements under the Paperwork Reduction Act of 1995. The reporting and recordkeeping requirements have been submitted to OMB for review. Executive Order 13132, “Federalism” It has been certified that this rule does not have federalism implications, as set forth in Executive Order 13132. This rule does not have substantial direct effects on:
(1)The States;
(2)The relationship between the National Government and the States; or
(3)The distribution of power and responsibilities among the various levels of Government. List of Subjects in 32 CFR Part 311 Privacy. Accordingly, 32 CFR part 311 is proposed to be revised to read as follows: PART 311—OFFICE OF THE SECRETARY OF DEFENSE PRIVACY PROGRAM Sec. 311.1 Purpose. 311.2 Applicability. 311.3 Definitions. 311.4 Policy. 311.5 Responsibilities. 311.6 Procedures. 311.7 Information requirements. Authority: Pub. L. 93-579, 88 Stat. 1986 (5 U.S.C. 552a). § 311.1 Purpose. This part updates and implement the policies and procedures outlined in 5 U.S.C. 552a, Office of Management and Budget
(OMB)Circular No. A-130, DoD Directive 5400.11, 1 and DoD 5400.11-R. 2 This part provides guidance and procedures for implementing the Privacy Program in the Office of the Secretary of Defense
(OSD)and organizations receiving administrative support from the Washington Headquarters Services (WHS), according to DoD Directive 5110.4. 3 1 Copies may be obtained at *http://www.dtic.mil/whs/directives/.* 2 Copies may be obtained at *http://www.dtic.mil/whs/directives/.* 3 Copies may be obtained at *http://www.dtic.mil/whs/directives/.* § 311.2 Applicability. This part:
(a)Applies to the OSD, the Chairman of the Joint Chiefs of Staff, and other activities receiving administrative support from the WHS (hereafter referred to collectively as the “OSD Components”).
(b)Covers systems of records maintained by the OSD Components and governs the maintenance, access, change, and release of information contained in those systems of records, from which information about an individual is retrieved by a personal identifier. § 311.3 Definitions. *Access.* Any individual's review of a record or a copy of a record or parts of a system of records. *Disclosure.* The transfer of any personal information from a system of records by any means of oral, written, electronic, mechanical, or other communication, to any person, private entity, or Government Agency, other than the subject of the record, the subject's designated agent, or the subject's guardian. *Individual.* A living citizen of the United States or an alien lawfully admitted to the United States for permanent residence. The legal guardian of an individual has the same rights as the individual and may act on his or her behalf. *Individual access.* Access to personal information pertaining to the individual, by the individual, his or her designated agent, or legal guardian. *Maintain.* For the purpose of this part, includes maintenance, collection, use, or dissemination. *Matching program.* A program that matches the personal records in computerized databases of two or more Federal Agencies using a computer. *Personal information.* Information about an individual that is intimate or private, as distinguished from information related solely to the individual's official functions or public life. *Records.* Any item, collection, or grouping of information, whatever the storage media ( *e.g.* , paper or electronic), about an individual that is maintained by an OSD Component, including, but not limited to, his or her education, financial transactions, medical history, criminal or employment history, and that contains his or her name, or the identifying number, symbol, or other identifying particular assigned to the individual, such as a finger or voice print or photograph. *System manager.* An OSD Component official who is responsible for the operation and management of a system of records. *System of records.* A group of records under the control of an OSD Component from which personal information is retrieved by the individual's name or by some identifying number, symbol, or other identifying particular assigned to an individual. § 311.4 Policy.
(a)According to DoD 5400.11-R, 4 it is DoD policy to safeguard personal information contained in any system of records maintained by any DoD Component and to permit any individual to know what existing records pertain to him or her. 4 Copies may be obtained at *http://www.dtic.mil/whs/directives/.*
(b)Each office maintaining records and information about individuals shall ensure that this data is protected from unauthorized disclosure. These offices shall permit individuals to have access to and have a copy made of all or any portion of records about them, except as provided in Chapters 3 and 5 of DoD 5400.11-R. The individuals will also have an opportunity to request that such records be amended as provided by 5 U.S.C. 552a and Chapter 3 of DoD 5400.11-R. Individuals requesting access to their records shall receive concurrent consideration under 5 U.S.C. 552 and 552a, if appropriate.
(c)The Heads of the OSD Components shall maintain any necessary record of a personal nature that is individually identifiable in a manner that complies with the law and DoD policy. Any information collected must be as accurate, relevant, timely, and complete as is reasonable to ensure fairness to the individual. Adequate safeguards must be provided to prevent misuse or unauthorized release of such information. § 311.5 Responsibilities.
(a)The Director, WHS, shall:
(1)Direct and administer the DoD Privacy Program for the OSD Components.
(2)Establish standards and procedures to ensure implementation of and compliance with 5 U.S.C. 552a, OMB Circular No. A-130, DoD Directive 5400.11 and DoD 5400.11-R.
(3)Ensure the Records and Declassification Division, Executive Services Directorate (ESD), WHS, implements all aspects of 5 U.S.C. 552a, except that portion about receiving and acting on public requests for personal records. As such, the Records and Declassification Division shall:
(i)Exercise oversight and administrative control of the Privacy Act Program for the OSD Components.
(ii)Provide guidance and training to the OSD Components as required by 5 U.S.C. 552a and OMB Circular A-130. Periodic training will be provided to public affairs officers and others who may be expected to deal with the news media or the public.
(iii)Collect and consolidate data from the OSD Components and submit reports to the Defense Privacy Office (DPO), as required by 5 U.S.C. 522a; OMB Circular A-130, DoD Directive 5400.11, DoD 5400.1-R, and the DPO.
(iv)Coordinate and consolidate information for reporting all record systems, as well as changes to approved systems, to the OMB, the Congress, and the **Federal Register** , as required by 5 U.S.C. 552a, OMB Circular A-130, and DoD 5400.1-R.
(v)Serve as the appellate authority for OSD Components when a requester appeals a denial for access to records under 5 U.S.C. 552a.
(vi)Serve as the appellate authority for OSD Components when a requester appeals a denial for amendment of a record or initiates legal action to correct a record.
(vii)Evaluate and decide, in coordination with the DPO, appeals resulting from denials of access or amendments to records by the OSD Components.
(4)Ensure the Freedom of Information Division, ESD, WHS, complies with all aspects of 5 U.S.C. 552a including that portion about receiving and acting on public requests for personal records. As such, the Freedom of Information Division shall:
(i)Forward requests for information or access to records to the appropriate OSD Component having primary responsibility for any pertinent system of records under 5 U.S.C. 552a or to the OSD Components under 5 U.S.C. 552.
(ii)Maintain deadlines to ensure responses are made within the time limits prescribed in 5 U.S.C. 552, DoD Instruction 5400.10 5 and this part. 5 Copies may be obtained at *http://www.dtic.mil/whs/directives/* .
(iii)Collect fees charged and assessed for reproducing requested materials.
(iv)Refer all matters about amendments of records and general and specific exemptions under 5 U.S.C. 552a to the proper OSD Components.
(5)Coordinate with the DoD General Counsel, or the WHS General Counsel when appropriate, on OSD Components' denials of appeals for amending records, and review actions to confirm denial of access to records, as appropriate.
(b)The DoD General Council shall provide advice and assistance to the:
(1)Chief, Records and Declassification Division, in the discharge of appellate and review responsibilities.
(2)Chief, Freedom of Information Division, on all access matters.
(3)OSD Component on legal matters pertaining to 5 U.S.C. 552a.
(c)The Heads of the OSD Components shall:
(1)Designate an individual as the point of contact for Privacy Act matters; advise the Chief, Records and Declassification Division, and the Chief, Freedom of Information Division, of the names of officials so designated.
(2)Report any new record system, or changes to an existing system, to the Chief, Records and Declassification Division, at least 90 days before the intended use of the system.
(3)Review all contracts pertaining to the maintenance of records systems, by or on behalf of the OSD Component, to ensure within his or her authority that language is included that provides such systems shall be maintained consistent with 5 U.S.C. 552a.
(4)Revise procurement guidance to ensure contracts providing for the maintenance of a records system, by or on behalf of the OSD Component, includes language that such system shall be maintained in accordance with 5 U.S.C. 552a.
(5)Ensure computer and telecommunications equipment or service procurements comply with 5 U.S.C. 552.
(6)Coordinate with the Chief, Information Officer, for the OSD Component to ensure a risk analysis is conducted in compliance with DoD 5400.11-R.
(7)Coordinate with the OSD Chief, Information Officer, to ensure a Privacy Impact Assessment is conducted in compliance with DoD CIO memorandum dated October 28, 2005 6 and DoD's implementing guidance. 6 Copies may be obtained from *http://www.dod.mil/privacy/DoD_PIA_Guidance_Oct_28_2005.pdf* .
(8)Ensure all DoD issuances prepared by the OSD Component that require forms or other methods to collect information about individuals are in compliance with 5 U.S.C. 552a.
(9)Establish internal administrative procedures to comply with the procedures listed in this part and DoD 5400.11-R.
(10)Coordinate with legal counsel on all proposed denials of access to records.
(11)Provide justification to the Freedom of Information Division when access to a record is denied in whole or in part.
(12)Provide the record of an initial denial or access to a record that is appealed to the Freedom of Information Division at the time of initial denial.
(13)Maintain an accurate accounting of the actions resulting in a denial for access to a record or for the correction of a record. This accounting should be maintained so it can be readily certified as the complete record of proceedings if litigation occurs in accordance with DoD 5400.11-R.
(14)Ensure all personnel who either have access to a system of records, or who are engaged in developing or overseeing the procedures for handling records in a system, are aware of their responsibilities for protecting personal information according to 5 U.S.C. 552a and DoD 5400.11-R.
(15)Forward all requests for access to records received directly from an individual to the Freedom of Information Division for appropriate suspense control and recording.
(16)Provide the Freedom of Information Division with a copy of the requested record when the request is granted.
(d)The requester shall:
(1)Submit a request for access to records pertaining to oneself in writing or in person to the OSD Component's custodian of the records. If the requester is not satisfied with the response, he or she may file another request in writing as provided in paragraph 311.1(b)(2). The requester must provide personal identification to verify identity according to Chapter 3 of DoD 5400.11-R and provide a signed notarized statement or a sworn declaration in the format specified by DoD 5400.7-R. 7 7 Copies may be obtained at *http://www.dtic.mil/whs/directives/* .
(2)Describe the record sought and provide sufficient information to enable the material to be located ( *e.g.* , identification of system of records, approximate date it was initiated, originating organization, and type of document).
(3)Comply with the procedures provided in DoD 5400.11-R for inspecting and/or obtaining copies of requested records.
(4)Submit a written request to amend a record to the office designated in the system of records notice. § 311.6 Procedures.
(a)Publication of notice in the **Federal Register** .
(1)A notice shall be published in the **Federal Register** of any record system meeting the definition of a system of records in DoD 5400.11-R.
(2)OSD Components shall provide the Chief, Records and Declassification Division, with 90 days advance notice of any anticipated new or revised system of records. This information shall be submitted to the OMB and Congress at least 60 days before use and published in the **Federal Register** at least 30 days before being put into use according to the procedures in DoD 5400.11-R. This provides the public with an opportunity to submit written data, views, or arguments to the OSD Components for consideration before a system of records is established or modified.
(b)*Access to systems of records information* .
(1)As provided by 5 U.S.C. 552a, records shall be disclosed only to the individual they pertain to and under whose individual name or identifier they are filed, unless exempted by the provisions in DoD 5400.11-R. If an individual is accompanied by a third party, the individual shall be required to furnish a signed access authorization which grants the third party access according to Chapter 3 of DoD 5400.11-R.
(2)Individuals may request access to their records, in person or by mail, in accordance with the following procedures:
(i)*In person* . Submit a request for an appointment in writing to WHS, ESD, Freedom of Information Division, 1155 Defense Pentagon, Washington, DC 20301-1155. The individual shall provide personal identification to the Freedom of Information Division to verify the individual's identity according to Chapter 3 of DoD 5400.11-R and provide a signed notarized statement or a sworn declaration in the format specified by DoD 5400.7-R.
(ii)*By mail* . Address requests to WHS, ESD, Freedom of Information Division, 1155 Defense Pentagon, Washington, DC 20301-1155. To verify the identity of the individual, the request shall include either a signed notarized statement or a sworn declaration in the format specified by DoD 5400.7-R.
(3)There is no requirement that an individual be given access to records that are not in a group of records that meet the definition of a system of records in 5 U.S.C. 552a.
(4)Granting access to a record containing personal information shall not be conditional upon any requirement that the individual state a reason or otherwise justify the need to gain access.
(5)No verification of identity shall be required of an individual seeking access to records that are otherwise available to the public.
(6)Individuals shall not be denied access to a record in a system of records about themselves because those records are exempted from disclosure under 5 U.S.C. 552. Individuals may only be denied access to a record in a system of records about themselves when those records are exempted from the access provisions of Chapter 5 of DoD 5400.11-R.
(7)Individuals shall not be denied access to their records for refusing to disclose their Social Security Number (SSN), unless disclosure of the SSN is required by statute, by regulation adopted before January 1, 1975, or if the record's filing identifier and only means of retrieval is by SSN.
(c)*Access to records or information compiled for law enforcement purposes* .
(1)Requests are processed under DoD Directive 5400.11 and 5 U.S.C. 552 to give requesters a greater degree of access to records on themselves.
(2)Records in the custody of law enforcement activities that have been incorporated into a system of records or exempted from the access conditions of DoD Directive 5400.11 will be processed in accordance with 5 U.S.C. 552. Individuals shall not be denied access to records solely because they are in the exempt system. They will have the same access that they would receive under 5 U.S.C. 552. (Also see section A.10., Chapter 3, DoD 5400.11-R)
(3)Records exempted from access conditions will be processed in accordance with DoD Directive 5400.11 or 5 U.S.C. 552, depending upon which regulation gives the greater degree of access. (See also section A.10.1., Chapter 3, DoD 5400.11-R)
(4)Records exempted from access under Section B, Chapter 5 of DoD 5400.11-R, that are temporarily in the custody of a non-law enforcement element for adjudicative or personnel actions, shall be referred to the originating agency.
(d)*Access to illegible, incomplete, or partially exempt records* .
(1)An individual shall not be denied access to a record or a copy of a record solely because the physical condition or format of the record does not make it readily available ( *e.g.* , deteriorated state or on magnetic tape). The document will be prepared as an extract, or it will be recopied exactly as is.
(2)If a portion of the record contains information that is exempt from access, an extract or summary containing all releasable information in the record shall be prepared.
(3)When the physical condition of the record makes it necessary to prepare an extract for release, the extract shall be prepared so that the requester will understand it.
(4)The requester shall be informed of all deletions or changes to records.
(e)*Access to medical records* .
(1)Medical records shall be disclosed to the individual and may be transmitted to a medical doctor named by the individual concerned.
(2)The individual may be charged reproduction fees for copies or records according to DoD 5400.11-R.
(f)*Amending and disputing personal information in systems of records* .
(1)The Head of an OSD Component, or a designated official, shall allow individuals to request amendment to their records to the extent that such records are not accurate, relevant, timely, or complete. Requests should be as brief and as simple as possible and should contain adequate identifying information to locate the record, a description of the items to be amended, and the reason for the change. A request shall not be rejected nor required to be resubmitted unless additional information is essential to process the request. Requesters shall be required to provide verification of their identity as stated in paragraph (b)(2) of this section to ensure they are seeking to amend records about themselves.
(2)The appropriate system of records system manager shall mail a written acknowledgment of an individual's request to amend a record within 10 workdays after receipt. Such acknowledgment shall identify the request and may, if necessary, request any additional information needed to make a determination. No acknowledgment is necessary if the request can be reviewed and processed, and the individual can be notified of compliance or denial, within the 10-day period. Whenever practical, the decision shall be made within 30 working days. For requests presented in person, written acknowledgment may be provided at the time the request is presented.
(3)*Amending personal information* . The Head of an OSD Component, or designated official, shall promptly take one of the following actions on requests to amend records:
(i)If they agree with any portion or all of an individual's request, amend the records in accordance with existing statutes, regulations, or internal administrative procedures, and inform the requester of the action taken. The OSD Component shall also notify all previous holders of the record that the amendment has been made and shall explain the substance of the correction, except for disclosures of the records to officers or DoD employees, or made as required by the Freedom of Information Act, the OSD shall also notify all to whom the record was disclosed that the amendment has been made and shall explain the substance of the correction.
(ii)Notify the requester of the disapproval to amend a record and the reason for the disapproval. Notify the requester of the procedure to submit an appeal as described in paragraph (f)(5) of this section. if he or she disagrees with all or any portion of a request.
(iii)Refer requests to the appropriate Federal Agency. Advise the requester of this referral if the request for an amendment pertains to a record controlled and maintained by another Agency.
(4)*Disputing personal information* . The Head of an OSD Component or designated official shall:
(i)Determine whether the requester has adequately supported his or her claim that the record is inaccurate, irrelevant, untimely, or incomplete.
(ii)Limit the review of a record to those items of information that clearly bear on any determination to amend the records and ensure that those elements are reviewed before a determination is made.
(5)If an individual disagrees with the initial OSD Component determination, he or she may file an appeal. The request should be sent to the Chief, Records and Declassification Division, WHS, 1155 Defense Pentagon, Washington, DC 20301-1155.
(6)If, after review, the Records and Declassification Division determines the system of records should not be amended as requested, the Records and Declassification Division shall provide a copy of any statement of disagreement to the extent that disclosure accounting is maintained in accordance with Chapter 4 or DoD 5400.11-R. The Records and Declassification Division shall advise the individual:
(i)Of the reason and authority for the denial.
(ii)Of his or her right to file a statement of the reason for disagreeing with the Records and Declassification Division decision.
(iii)Of the procedures for filing a statement of disagreements.
(iv)That the statement filed shall be made available to anyone the record is disclosed to, together with a brief statement summarizing reasons for refusing to amend the records.
(7)If the Records and Declassification Division determines that the record should be amended in accordance with the individual's request, the OSD Component shall amend the record, and advise the individual of the amendment, in accordance with Chapter 4 of DoD 5400.11-R.
(8)All appeals should be processed within 30 workdays after receipt. If the Records and Declassification Division determines that a fair and equitable review cannot be made within that time, the individual shall be informed in writing of the reasons for the delay and of the approximate date the review is expected to be completed.
(g)*Disclosure of disputed information.*
(1)If the Records and Declassification Division determines the record should not be amended and the individual has filed a statement of disagreement under paragraph (f)(7) of this section, the OSD Component shall annotate the disputed record so it is apparent under record disclosure that a statement has been filed. Where feasible, the notation itself shall be integral to the record. Where disclosure accounting has been made, the OSD Component shall advise previous recipients that the record has been disputed and shall provide a copy of the individual's statement of disagreement in accordance with Chapter 4 of DoD 5400.11-R.
(i)This statement shall be maintained to permit ready retrieval whenever the disputed portion of the record is disclosed.
(ii)When information that is the subject of a statement of disagreement is subsequently disclosed, the OSD Component's designated official shall note which information is disputed and provide a copy of the individual's statement.
(2)The OSD Component shall include a brief summary of its reasons for not making a correction when disclosing disputed information. Such statements shall normally be limited to the reasons given to the individual for not amending the record.
(3)Copies of the OSD Component's summary will be treated as part of the individual's record; however, it will not be subject to the amendment procedure outlined in paragraph (c)(3) of this section.
(h)*Penalties.*
(1)*Civil action.* An individual may file a civil suit against the OSD Component or its employees if the individual feels certain provisions or the Privacy Act have been violated as stated in 5 U.S.C. 552a.
(2)*Criminal action.*
(i)Criminal penalties may be imposed against an OSD officer or employee for offenses listed in Section
(i)of 5 U.S.C. 552a, as follows:
(A)Willful unauthorized disclosure of protected information in the records.
(B)Failure to publish a notice of the existence of a record system in the **Federal Register** .
(C)Requesting or gaining access to the individual's record under false pretenses.
(ii)An OSD officer or employee may be fined up to $5,000 for a violation as outlined in paragraph (h)(2)(i) of this section.
(i)*Litigation status sheet.* Whenever a complaint citing 5 U.S.C. 552a is filed in a U.S. District Court against the Department of Defense, an OSD Component, or any OSD employee, the responsible system manager shall promptly notify the DPO. The litigation status sheet in DoD 5400.11-R provides a standard format for this notification. (The initial litigation status sheet shall, as a minimum, provide the information required by items 1, through 6. of DoD 5400.11-R) A revised litigation status sheet shall be provided at each stage of the litigation. When a court renders a formal opinion or judgment, copies of the judgment or opinion shall be provided to the DPO with the litigation status sheet reporting that judgment or opinion.
(j)*Computer matching programs.* Chapter 11, paragraph B of DoD 5400.11-R, prescribes that all requests for participation in a matching program (either as a matching agency or a source agency) be submitted to the DPO for review and compliance. The OSD Components shall submit these requests through the Records and Declassification Division. § 311.7 Information requirements. The DPO shall establish requirements and deadlines for DoD privacy reports. These reports shall be licensed in accordance with DoD Directive 8910.1. 8 8 Copies may be obtained at *http://www.dtic.mil/whs/directives/* Dated: January 16, 2007. L.M. Bynum, Alternate OSD Federal Register Liaison Officer, DoD. [FR Doc. E7-800 Filed 1-22-07; 8:45 am] BILLING CODE 5001-06-P ENVIRONMENTAL PROTECTION AGENCY 40 CFR Part 52 [EPA-R05-OAR-2005-OH-0005; FRL-8272-9] Approval and Promulgation of Implementation Plans; Ohio Particulate Matter AGENCY: Environmental Protection Agency (EPA). ACTION: Proposed rule. SUMMARY: EPA is re-proposing approval of Ohio rules concerning equivalent visible emission limits (EVELs). Ohio's rules provide criteria for establishment of EVELs, and the rules provide that EVELs established according to these criteria take effect without formal review by EPA. EPA proposed to approve these rules on December 2, 2002, at 67 FR 71515. However, that proposal did not clearly solicit comment on the timing by which actions on EVELs by the State take effect. EPA is proposing that previous State modifications to EVELs would become effective at the federal level immediately upon the effective date of any final EPA action approving these Ohio rules. Similarly, any future action by the State to establish, modify, or rescind EVELs in accordance with the criteria given in these Ohio rules would become effective at the federal level immediately upon the effective date of the State action. DATES: Written comments on this proposed rule must arrive on or before February 22, 2007. ADDRESSES: Submit your comments, identified by Docket ID No. EPA-R05-OAR-2005-OH-0005, by one of the following methods: • *www.regulations.gov:* Follow the on-line instructions for submitting comments. • *E-mail: mooney.john@epa.gov.* • *Fax:*
(312)886-5824. • *Mail:* John M. Mooney, Chief, Criteria Pollutant Section, Air Programs Branch, (AR-18J), U.S. Environmental Protection Agency, 77 West Jackson Boulevard, Chicago, Illinois 60604. • *Hand Delivery:* John M. Mooney, Chief, Criteria Pollutant Section, Air Programs Branch, (AR-18J), U.S. Environmental Protection Agency, 77 West Jackson Boulevard, Chicago, Illinois 60604. Such deliveries are only accepted during the Regional Office normal hours of operation, and special arrangements should be made for deliveries of boxed information. The Regional Office official hours of business are Monday through Friday, 8:30 a.m. to 4:30 p.m. excluding Federal holidays. *Instructions:* Direct your comments to Docket ID No. EPA-R05-OAR-2005-OH-0005. EPA's policy is that all comments received will be included in the public docket without change and may be made available online at *www.regulations.gov,* including any personal information provided, unless the comment includes information claimed to be Confidential Business Information
(CBI)or other information whose disclosure is restricted by statute. Do not submit information that you consider to be CBI or otherwise protected through *www.regulations.gov* or e-mail. The *www.regulations.gov* Web site is an “anonymous access” system, which means EPA will not know your identity or contact information unless you provide it in the body of your comment. If you send an e-mail comment directly to EPA without going through *www.regulations.gov* your e-mail address will be automatically captured and included as part of the comment that is placed in the public docket and made available on the Internet. If you submit an electronic comment, EPA recommends that you include your name and other contact information in the body of your comment and with any disk or CD-ROM you submit. If EPA cannot read your comment due to technical difficulties and cannot contact you for clarification, EPA may not be able to consider your comment. Electronic files should avoid the use of special characters, any form of encryption, and be free of any defects or viruses. For additional instructions on submitting comments, go to Section I of the SUPPLEMENTARY INFORMATION section of this document. *Docket:* All documents in the docket are listed in the *www.regulations.gov index.* Although listed in the index, some information is not publicly available, e.g., CBI or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, will be publicly available only in hard copy. Publicly available docket materials are available either electronically in *www.regulations.gov* or in hard copy at the Environmental Protection Agency, Region 5, Air and Radiation Division, 77 West Jackson Boulevard, Chicago, Illinois 60604. This Facility is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. We recommend that you telephone John Summerhays, Environmental Scientist, at
(312)886-6067 before visiting the Region 5 office. FOR FURTHER INFORMATION CONTACT: John Summerhays, Environmental Scientist, Criteria Pollutant Section, Air Programs Branch (AR-18J), Environmental Protection Agency, Region 5, 77 West Jackson Boulevard, Chicago, Illinois 60604,
(312)886-6067, *summerhays.john@epa.gov.* SUPPLEMENTARY INFORMATION: This supplementary information section is arranged as follows: I. What action is EPA taking today? II. What Should I Consider as I Prepare My Comments for EPA? III. Statutory and Executive Order Reviews I. What action is EPA taking today? EPA is re-proposing to approve Ohio rules providing for State issuance of equivalent visible emission limits (EVELs), rules which were a part of a set of particulate matter regulations that Ohio submitted on July 18, 2000. EPA originally proposed to approve these rules on December 2, 2002, at 67 FR 71515. However, that proposal did not clearly explain EPA's views regarding the consequences of approval on historic EVELs that were previously approved into the State Implementation Plan (SIP). EPA today is explaining its views and soliciting comment on this issue. The rules that EPA proposes to approve provide that EVELs issued by the State in accordance with the specified criteria take effect without formal review by EPA. Consequently, when the State issues an EVEL for a unit at a source, this EVEL will supersede any EVEL that may previously have been issued for that unit, regardless of whether or not the prior EVEL was part of the SIP. Similar consequences apply when the State terminates an EVEL for a unit at a source, presumably by issuing a permit or other enforceable document that re-establishes the standard opacity limits of OAC 3745-17-07 (A)(1) as the applicable opacity limits; that action will terminate the EVEL for that unit, again regardless of whether the prior EVEL was part of the SIP. EPA's understanding is that the State will periodically review whether previously issued EVELs are still warranted, as part of its management of the EVELs that apply in the State. EPA is proposing that, as of the effective date of EPA finalizing this proposal, no EVEL shall apply unless Ohio has issued a currently effective EVEL in accordance with its Rule 3745-17-07(C), and the federally enforceable level of any such EVEL shall reflect the currently effective EVEL that the State has thus issued. Therefore, EPA is proposing to delete provisions of the Ohio SIP that contain EVELs, in particular paragraphs (c)(62) and (c)(65) of 40 CFR 52.1870. EPA recognizes that the Ohio SIP contains other EVELs, implicitly included in SIP-approved permits or administrative orders that also contain other limits. For administrative convenience, EPA proposes not to modify the text of the SIP codification given in 40 CFR 52.1870 to discontinue these EVELs explicitly. Nevertheless, EPA proposes that when this proposed rulemaking becomes final and effective, these EVELs will automatically be discontinued and replaced by the opacity limits that Ohio has adopted more recently in accordance with the criteria given in Rule 3745-17-07(C). (The more recent permits or administrative orders may or may not have limits matching the prior SIP limits.) Similarly, EPA proposes that any future State action to establish, modify, or rescind opacity limits in accordance with the criteria in Rule 3745-17-07(C) shall immediately alter the federal opacity limit accordingly. II. What Should I Consider as I Prepare My Comments for EPA? *When submitting comments, remember to:* 1. Identify the rulemaking by docket number and other identifying information (subject heading, **Federal Register** date and page number). 2. Follow directions—The EPA may ask you to respond to specific questions or organize comments by referencing a Code of Federal Regulations
(CFR)part or section number. 3. Explain why you agree or disagree; suggest alternatives and substitute language for your requested changes. 4. Describe any assumptions and provide any technical information and/or data that you used. 5. If you estimate potential costs or burdens, explain how you arrived at your estimate in sufficient detail to allow for it to be reproduced. 6. Provide specific examples to illustrate your concerns, and suggest alternatives. 7. Explain your views as clearly as possible, avoiding the use of profanity or personal threats. 8. Make sure to submit your comments by the comment period deadline identified. III. Statutory and Executive Order Reviews Executive Order 12866; Regulatory Planning and Review Under Executive Order 12866 (58 FR 51735, September 30, 1993), this action is not a “significant regulatory action” and, therefore, is not subject to review by the Office of Management and Budget. Paperwork Reduction Act This proposed rule does not impose an information collection burden under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 *et seq.* ). Regulatory Flexibility Act This proposed action merely proposes to approve state law as meeting Federal requirements and imposes no additional requirements beyond those imposed by state law. Accordingly, the Administrator certifies that this proposed rule will not have a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601 et seq.). Unfunded Mandates Reform Act Because this rule proposes to approve pre-existing requirements under state law and does not impose any additional enforceable duty beyond that required by state law, it does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4). Executive Order 13132 Federalism This action also does not have Federalism implications because it does not have substantial direct effects on the states, on the relationship between the national government and the states, or on the distribution of power and responsibilities among the various levels of government, as specified in Executive Order 13132 (64 FR 43255, August 10, 1999). This action merely proposes to approve a state rule implementing a Federal standard, and does not alter the relationship or the distribution of power and responsibilities established in the Clean Air Act. Executive Order 13175 Consultation and Coordination With Indian Tribal Governments This proposed rule also does not have tribal implications because it will not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes, as specified by Executive Order 13175 (65 FR 67249, November 9, 2000). Executive Order 13045 Protection of Children From Environmental Health and Safety Risks This proposed rule also is not subject to Executive Order 13045 “Protection of Children from Environmental Health Risks and Safety Risks” (62 FR 19885, April 23, 1997), because it is not economically significant. Executive Order 13211 Actions That Significantly Affect Energy Supply, Distribution, or Use Because it is not a “significant regulatory action” under Executive Order 12866 or a “significant regulatory action,” this action is also not subject to Executive Order 13211, “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use” (66 FR 28355, May 22, 2001). National Technology Transfer Advancement Act Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (NTTAA), 15 U.S.C. 272, requires Federal agencies to use technical standards that are developed or adopted by voluntary consensus to carry out policy objectives, so long as such standards are not inconsistent with applicable law or otherwise impractical. In reviewing SIP submissions, EPA's role is to approve state choices, provided that they meet the criteria of the Clean Air Act. Absent a prior existing requirement for the state to use voluntary consensus standards, EPA has no authority to disapprove a SIP submission for failure to use such standards, and it would thus be inconsistent with applicable law for EPA to use voluntary consensus standards in place of a program submission that otherwise satisfies the provisions of the Clean Air Act. Therefore, the requirements of section 12(d) of the NTTA do not apply. List of Subjects in 40 CFR Part 52 Environmental protection, Air pollution control, Intergovernmental relations, Particulate matter. Dated: January 11, 2007. Mary A. Gade, Regional Administrator [FR Doc. E7-923 Filed 1-22-07; 8:45 am] BILLING CODE 6560-50-P ENVIRONMENTAL PROTECTION AGENCY 40 CFR Parts 52 and 81 [EPA-R06-OAR-2006-0386; FRL-8272-6] Approval and Promulgation of Implementation Plans; Texas; El Paso County Carbon Monoxide Redesignation to Attainment, and Approval of Maintenance Plan AGENCY: Environmental Protection Agency (EPA). ACTION: Proposed rule. SUMMARY: On January 20, 2006, the Texas Commission on Environmental Quality
(TCEQ)submitted a State Implementation Plan
(SIP)revision to request redesignation of the El Paso carbon monoxide
(CO)nonattainment area to attainment for the CO National Ambient Air Quality Standard (NAAQS). This submittal also included a CO maintenance plan for the El Paso area and associated Motor Vehicle Emission Budgets (MVEBs). The maintenance plan was developed to ensure continued attainment of the CO NAAQS for a period of 10 years from the effective date of EPA approval of redesignation to attainment. In this action, EPA is proposing to approve the El Paso CO redesignation request and the maintenance plan with its associated MVEBs as satisfying the requirements of the Federal Clean Air Act
(CAA)as amended in 1990. DATES: Written comments must be received by February 22, 2007. ADDRESSES: Comments may be mailed to Mr. Thomas Diggs, Chief, Air Planning Section (6PD-L), Environmental Protection Agency, 1445 Ross Avenue, Suite 1200, Dallas, Texas 75202-2733. Comments may also be submitted electronically or through hand delivery/ courier by following the detailed instructions in the ADDRESSES section of the direct final rule located in the rules section of this **Federal Register** . FOR FURTHER INFORMATION CONTACT: Jeffrey Riley, Air Planning Section (6PD-L), Environmental Protection Agency, Region 6, 1445 Ross Avenue, Suite 700, Dallas, Texas 75202-2733, telephone 214-665-8542; fax number 214-665-7263; e-mail address *riley.jeffrey@epa.gov.* SUPPLEMENTARY INFORMATION: I. Why Is EPA Issuing This Proposed Rule? This document proposes to take action on SIP revisions pertaining to the El Paso area. We have published a direct final rule approving the State's SIP revisions in the “Rules and Regulations” section of this **Federal Register** because we view this as a noncontroversial action and anticipate no adverse comment. We have explained our reasons for this action in the preamble to the direct final rule. If we receive no adverse comment, we will not take further action on this proposed rule. If we receive adverse comment, we will withdraw the direct final rule and it will not take effect. We would address all public comments in any subsequent final rule based on this proposed rule. We do not intend to institute a second comment period on this action. Any parties interested in commenting must do so at this time. For further information, please see the information provided in the ADDRESSES section of this document. Dated: January 11, 2007. Richard E. Greene, Acting Regional Administrator, Region 6. [FR Doc. E7-925 Filed 1-22-07; 8:45 am] BILLING CODE 6560-50-P DEPARTMENT OF HOMELAND SECURITY Federal Emergency Management Agency 44 CFR Part 67 [Docket No. FEMA-D-7688] Proposed Flood Elevation Determinations AGENCY: Federal Emergency Management Agency, DHS. ACTION: Proposed rule. SUMMARY: Technical information or comments are requested on the proposed Base (1% annual chance) Flood Elevations
(BFEs)and proposed BFEs modifications for the communities listed below. The BFEs are the basis for the floodplain management measures that the community is required either to adopt or to show evidence of being already in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP). DATES: The comment period is ninety
(90)days following the second publication of this proposed rule in a newspaper of local circulation in each community. ADDRESSES: The proposed BFEs for each community are available for inspection at the office of the Chief Executive Officer of each community. The respective addresses are listed in the table below. FOR FURTHER INFORMATION CONTACT: William R. Blanton, Jr., Engineering Management Section, Mitigation Division, Federal Emergency Management Agency, 500 C Street, SW., Washington, DC 20472,
(202)646-3151. SUPPLEMENTARY INFORMATION: The Federal Emergency Management Agency
(FEMA)proposes to make determinations of BFEs and modified BFEs for each community listed below, in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR 67.4(a). These proposed BFEs and modified BFEs, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own, or pursuant to policies established by other Federal, State or regional entities. These proposed elevations are used to meet the floodplain management requirements of the NFIP and are also used to calculate the appropriate flood insurance premium rates for new buildings built after these elevations are made final, and for the contents in these buildings. *National Environmental Policy Act.* This proposed rule is categorically excluded from the requirements of 44 CFR part 10, Environmental Consideration. An environmental impact assessment has not been prepared. *Regulatory Flexibility Act.* As flood elevation determinations are not within the scope of the Regulatory Flexibility Act, 5 U.S.C. 601-612, a regulatory flexibility analysis is not required. *Regulatory Classification.* This proposed rule is not a significant regulatory action under the criteria of section 3(f) of Executive Order 12866 of September 30, 1993, Regulatory Planning and Review, 58 FR 51735. *Executive Order 13132, Federalism.* This proposed rule involves no policies that have federalism implications under Executive Order 13132. *Executive Order 12988, Civil Justice Reform.* This proposed rule meets the applicable standards of Executive Order 12988. List of Subjects in 44 CFR Part 67 Administrative practice and procedure, Flood insurance, Reporting and recordkeeping requirements. Accordingly, 44 CFR part 67 is proposed to be amended as follows: PART 67—[AMENDED] 1. The authority citation for part 67 continues to read as follows: Authority: 42 U.S.C. 4001 *et seq.* ; Reorganization Plan No. 3 of 1978, 3 CFR, 1978 Comp., p. 329; E.O. 12127, 44 FR 19367, 3 CFR, 1979 Comp., p. 376. § 67.4 [Amended] 2. The tables published under the authority of § 67.4 are proposed to be amended as follows: Flooding source(s) Location of referenced elevation * Elevation in feet
(NGVD)+Elevation in feet
(NAVD)# Depth in feet above ground Effective Modified Communities affected Camden County, New Jersey (All Jurisdictions) Barton Run Tributary 3 At State Route 73 +85 +84 Township of Voorhees. Approximately 1,040 feet above Sunset Avenue None +134 Cooper River Approximately 180 feet upstream of Kaighns Avenue (County Route 607) +9 +10 City of Camden, Borough of Collingswood, Township of Cherry Hill, Borough of Gibbsboro, Township of Haddon, Borough of Haddonfield, Borough of Lawnside, Borough of Lindenwold, Township of Pennsauken, Borough of Somerdale, Borough of Tavistock, Township of Voorhees. Approximately 155 feet upstream of Gibbsboro Road None +73 Mason Run Approximately 50 feet downstream of Clementon Road County Route 683 +23 +25 Borough of Lindenwold. Approximately 125 feet upstream of County Route 534 None +35 Millard Creek At the confluence with Cooper River +65 +64 Borough of Gibbsboro. Approximately 500 feet upstream of Gibbsboro Road (County Route 686) None +76 Newton Creek Approximately 10 feet downstream of White Horse Pike +9 +10 Borough of Audubon, Borough of Collingswood, Township of Haddon, Borough of Haddonfield, Borough of Oaklyn. Approximately 140 feet upstream of West End Avenue None +47 Nicholson Branch At confluence with Millard Creek +65 +67 Borough of Gibbsboro, Township of Voorhees. Approximately 590 feet upstream of North Lake Drive None +100 North Branch At confluence with Cooper River +16 +14 Township of Cherry Hill, Township of Voorhees. Cooper River Approximately 0.48 mile upstream of Kresson Road (County Route 671) None +86 South Branch Newton Creek Approximately 60 feet upstream of abandoned railroad +9 +10 Borough of Audubon, Township of Haddon, City of Gloucester, Township of Mount Ephraim. Approximately 500 feet upstream of State Route 168 None +11 Tributary No. 1 to Cooper River At confluence with Cooper River +39 +38 Township of Cherry Hill. At downstream side of Burnt Mill Road +41 +40 Tributary No. 2 At confluence with Cooper River +40 +38 Township of Cherry Hill. At downstream side of Evesham Road +59 +60 Tributary No. 3 At confluence with Cooper River +43 +42 Borough of Lawnside, Borough of Somerdale, Township of Voorhees. Approximately 500 feet upstream of Evesham Road +54 +55 Tributary No. 4 At confluence with Cooper River +53 +52 At downstream side of Rural Avenue +53 +52 Signey Run Approximately 1,100 feet upstream confluence with North Branch Big Timber Creek +15 +16 Township of Gloucester, Borough of Hi-Nella, Borough of Stratford. At downstream side of Warwick Road +43 +42 Tributary No. 1 to North Branch Cooper River At confluence with North Branch Cooper River +71 +76 Township of Voorhees. At downstream side of Kresson Road +101 +100 Tributary No. 2 At confluence with North Branch Cooper River +77 +82 Township of Voorhees. Approximately 900 feet upstream of confluence with North Branch Cooper River +81 +82 Peter Brook At confluence with Newton Creek None +9 Borough of Audubon Park, Borough of Oaklyn. At approximately 0.92 mile upstream Newton Creek None +9 North Branch Big Timber At downstream side of East Atlantic Avenue (County Route 727) None +41 Borough of Clementon. At approximately 1,950 feet upstream of East Atlantic Avenue (County Route 727) None +41 * National Geodetic Vertical Datum. # Depth in feet above ground. + North American Vertical Datum. ADDRESSES Borough of Audubon Maps are available for inspection at the Borough of Audubon, 606 West Nicholson Road, Audubon, New Jersey. Send comments to The Honorable Anthony M. Pugliese, Mayor of the Borough of Audubon, 606 West Nicholson Road, Audubon, New Jersey 08106. Borough of Audubon Park Maps are available for inspection at the Borough of Audubon Park, 20 Road C, Audubon Park, New Jersey. Send comments to The Honorable Donald M. Pennock, Mayor of the Borough of Audubon Park, 20 Road C, Audubon Park, New Jersey 08106. City of Camden Maps are available for inspection at the City of Camden Planning Department, 520 Market Street, Room 422, Camden, New Jersey. Send comments to The Honorable Gwendolyn A. Faison, Mayor of the City of Camden, P.O. Box 95120, Camden, New Jersey 08101. Township of Cherry Hill Maps are available for inspection at the Cherry Hill Township Building, 820 Mercer Street, Cherry Hill, New Jersey. Send comments to The Honorable Bernie Platt, Mayor of the Township of Cherry Hill, 820 Mercer Street, Cherry Hill, New Jersey 08002. Borough of Clementon Maps are available for inspection at the Borough of Clementon, 101 Gibbsboro Road, Clementon, New Jersey. Send comments to The Honorable Mark E. Armbruster, Mayor of the Borough of Clementon, 101 Gibbsboro Road, Clementon, New Jersey. Borough of Collingswood Maps are available for inspection at the Borough of Collingswood, 678 Haddon Avenue, Collingswood, New Jersey. Send comments to The Honorable Jim Maley, Mayor of the Borough of Collingswood, 678 Haddon Avenue, Collingswood, New Jersey 08108. Borough of Gibbsboro Maps are available for inspection at the Gibbsboro Borough Hall, 49 Kirkwood Drive, Gibbsboro, New Jersey. Send comments to The Honorable Edward G. Campbell, III, Mayor of the Borough of Gibbsboro, 49 Kirkwood Drive, Gibbsboro, New Jersey 08026. City of Gloucester Maps are available for inspection at the City of Gloucester Municipal Building, 313 Monmouth Street, Gloucester, New Jersey. Send comments to The Honorable Thomas J. Kilcourse, Mayor of the City of Gloucester, 313 Monmouth Street, Gloucester, New Jersey 08030. Township of Gloucester Maps are available for inspection at the Township of Gloucester Municipal Building, 1261 Chews Landing Road, Blackwood, New Jersey. Send comments to The Honorable Cindy Rau-Hatton, Mayor of the Township of Gloucester, P.O. Box 8, CS #5, Blackwood, New Jersey 08012-0008. Township of Haddon Maps are available for inspection at the Township of Haddon Municipal Building, 135 Haddon Avenue, Westmont, New Jersey. Send comments to The Honorable William J. Park, Jr., Mayor of the Township of Haddon, 135 Haddon Avenue, Westmont, New Jersey 08108. Borough of Haddonfield Maps are available for inspection at the Borough of Haddonfield, 242 Kings Highway East, Haddonfield, New Jersey. Send comments to The Honorable Leticia Colombi, Mayor of the Borough of Haddonfield, P.O. Box 3005, Haddonfield, New Jersey 08033. Borough of Hi-Nella Maps are available for inspection at the Hi-Nella Borough Hall, 100 Wykagl Road, Hi-Nella, New Jersey. Send comments to The Honorable Ellen Wolica, Mayor of the Borough of Hi-Nella, 100 Wykagl Road, Hi-Nella, New Jersey 08038. Borough of Lawnside Maps are available for inspection at the Borough of Lawnside Zoning Department, 4 North Douglas Avenue, Lawnside, New Jersey. Send comments to The Honorable Mark Bryant, Mayor of the Borough of Lawnside, 4 North Douglas Avenue, Lawnside, New Jersey 08045. Borough of Lindenwold Maps are available for inspection at the Borough of Lindenwold Construction Office, 2001 Egg Harbor Road, Lindenwold, New Jersey. Send comments to The Honorable Frank DeLucca, Jr., Mayor of the Borough of Lindenwold, 2001 Egg Harbor Road, Lindenwold, New Jersey 08021. Borough of Mount Ephraim Maps are available for inspection at the Borough of Mt. Ephraim Tax Office, 121 South Black Horse Pike, Mount Ephraim, New Jersey. Send comments to The Honorable Michael Reader, Mayor of the Borough of Mount Ephraim, 121 South Black Horse Pike, Mount Ephraim, New Jersey 08059. Borough of Oaklyn Maps are available for inspection at the Borough of Oaklyn, 500 White Horse Pike, Oaklyn, New Jersey 08107. Send comments to The Honorable Michael LaMaina, Mayor of the Borough of Oaklyn, 500 White Horse Pike, Oaklyn, New Jersey. Township of Pennsauken Maps are available for inspection at the Pennsauken Municipal Building, Administration Office, 5605 North Crescent Boulevard, Pennsauken, New Jersey. Send comments to The Honorable Greg Schofield, Mayor of the Township of Pennsauken, 5605 North Crescent Boulevard, Pennsauken, New Jersey 08110. Borough of Somerdale Maps are available for inspection at the Somerdale Borough Hall, 105 Kennedy Boulevard, Somerdale, New Jersey. Send comments to The Honorable Gary Passanante, Mayor of the Borough of Somerdale, 105 Kennedy Boulevard, Somerdale, New Jersey 08083. Borough of Stratford Maps are available for inspection at the Borough of Stratford, 307 Union Avenue, Stratford, New Jersey. Send comments to The Honorable Thomas Angelucci, Mayor of the Borough of Stratford, 307 Union Avenue, Stratford, New Jersey 08084. Borough of Tavistock Maps are available for inspection at the Borough of Tavistock, Remington and Vernick Engineering, 232 Kings Highway, Haddonfield, New Jersey. Send comments to The Honorable George J. Buff, III, Mayor of the Borough of Tavistock, P.O. Box 8988, Turnersville, New Jersey 08012. Township of Voorhees Maps are available for inspection at the Township of Voorhees, Municipal Clerk's Office, 620 Berlin Road, Voorhees, New Jersey. Send comments to The Honorable Michael R. Mignogna, Mayor of the Township of Voorhees, 620 Berlin Road, Voorhees, New Jersey 08043. Passaic County, New Jersey (All Jurisdictions) Molly Ann Brook From the downstream side of Sherwood Avenue +125 +124 Borough of Haledon, Borough of Prospect Park, City of Paterson. Approximately 825 feet upstream of the weir +184 +185 * National Geodetic Vertical Datum. # Depth in feet above ground. + North American Vertical Datum. ADDRESSES Borough of Haledon Maps are available for inspection at the Haledon Borough Hall, 510 Belmont Avenue, Haledon, New Jersey. Send comments to The Honorable Ken Pengitore, Mayor of the Borough of Haledon, 510 Belmont Avenue, Haledon, New Jersey 07508. Borough of Prospect Park Maps are available for inspection at the Prospect Park Borough Hall, 106 Brown Avenue, Prospect Park, New Jersey. Send comments to The Honorable Mohamed T. Kahairullah, Mayor of the Borough of Prospect Park, 106 Brown Avenue, Prospect Park, New Jersey 07508. City of Paterson Maps are available for inspection at the Paterson City Hall, 155 Market Street, Passaic, New Jersey. Send comments to The Honorable Jose Torres, Mayor of the City of Paterson, 155 Market Street, Passaic, New Jersey 07505. Somerset County, New Jersey (All Jurisdictions) Chambers Brook #1 At confluence with North Branch Raritan River +79 +80 Township of Bedminster. Approximately 0.5 mile above the confluence with North Branch Raritan River +79 +80 #2 At confluence with North Branch Raritan River +70 +74 Township of Branchburg. Approximately 0.4 mile above the confluence with North Branch Raritan River +73 +74 Cory's Brook At the confluence with Passaic River +214 +213 Township of Warren. Approximately 1,800 feet upstream of Powder Horn Road None +405 Cuckels Brook At confluence with Raritan River +37 +39 Township of Bridgewater. Approximately 0.92 mile upstream of confluence with Raritan River +41 +42 Green Brook At confluence with Raritan River +32 +33 Borough of Bound Brook. Approximately 200 feet downstream Conrail +32 +33 Harrison Brook Branch 1 At confluence with Harrison Brook +222 +220 Township of Bernards. At Lurlin Drive +230 +231 Indian Grave Brook At confluence with Passaic River +297 +304 Township of Bernards, Borough of Bernardsville. Approximately 100 feet downstream of County boundary +611 +610 Millstone River At confluence with Raritan River +39 +41 Township of Franklin, Borough of Manville. At confluence of Royce Brook +40 +41 Moggy Brook At confluence with North Branch None +125 Borough of Far Hills. Approximately 0.55 mile upstream of the confluence with North Branch Raritan River +154 +156 Neshanic River At the confluence with South Branch Raritan River +81 +82 Township of Hillsborough. Approximately 1.73 miles upstream of Montgomery Road +103 +102 North Branch Raritan River Tributary C At confluence with North Branch Raritan River +196 +197 Borough of Bernardsville. Approximately 400 feet upstream of confluence with North Branch Raritan River +209 +210 Peters Brook At confluence with Raritan River +46 +48 Township of Bridgewater. Approximately 900 feet downstream of North Bridge Street +48 +49 Ross Brook At confluence with Peter's Brook +46 +48 Township of Bridgewater, Borough of Somerville. Approximately 45 feet downstream of Spring Street +47 +48 Royce Brook At confluence with Millstone River +40 +41 Borough of Manville. Approximately 0.4 mile upstream of confluence with Millstone River +40 +41 Tributary K At confluence with Indian Grave Brook +449 +455 Borough of Bernardsville. Approximately 1,670 feet upstream of Washington Corner Road +562 +564 * National Geodetic Vertical Datum. # Depth in feet above ground. + North American Vertical Datum. ADDRESSES Township of Bedminster Maps are available for inspection at the Bedminster Township Hall, One Miller Lane, Bedminster, New Jersey. Send comments to The Honorable Robert Holtaway, Mayor of the Township of Bedminster, One Miller Lane, Bedminster, New Jersey 07921. Township of Bernards Maps available for inspection at the Township of Bernards Engineering Services Building, 277 South Maple Avenue, Basking Ridge, New Jersey. Send comments to The Honorable John Malay, Mayor of the Township of Bernards, 1 Collyer Lane, Basking Ridge, New Jersey 07920. Borough of Bernardsville Maps available for inspection at the Bernardsville Municipal Building, 166 Mine Brook Road, Bernardsville, New Jersey. Send comments to The Honorable Jay Parsons, Mayor of the Borough of Bernardsville, 166 Mine Brook Road, Bernardsville, New Jersey 07924. Borough of Bound Brook Maps available for inspection at the Bound Brook Borough Office, 230 Hamilton Street, Bound Brook, New Jersey. Send comments to Mr. John J. Kennedy, Bound Brook Borough Administrator, 230 Hamilton Street, Bound Brook, New Jersey 08805. Township of Branchburg Maps available for inspection at the Branchburg Township Engineering Department, 1077 Route 202 North, Branchburg, New Jersey. Send comments to The Honorable Kate Sarles, Mayor of the Township of Branchburg, 1077 Route 202 North, Branchburg, New Jersey 08876. Township of Bridgewater Maps available for inspection at the Bridgewater Township Code Enforcement Office, 700 Garretson Road, Bridgewater, New Jersey. Send comments to The Honorable Patricia Flannery, Mayor of the Township of Bridgewater, 700 Garretson Road, Bridgewater, New Jersey 08807. Borough of Far Hills Maps available for inspection at the Far Hills Borough Municipal Building, 6 Prospect Street, Far Hills, New Jersey. Send comments to The Honorable Carl J. Torsilieri, Mayor of the Borough of Far Hills, 6 Prospect Street, Far Hills, New Jersey 07931. Township of Franklin Maps available for inspection at the Franklin Township Engineering Department, 475 De Mott Lane, Somerset, New Jersey. Send comments to Mr. Kenneth W. Daly, Franklin Township Manager, 475 De Mott Lane, Somerset, New Jersey 08873. Township of Hillsborough Maps available for inspection at the Hillsborough Township Municipal Complex, 379 South Branch Road, Hillsborough, New Jersey. Send comments to The Honorable Carl Suraci, Mayor of the Township of Hillsborough, Hillsborough Township Municipal Complex, 379 South Branch Road, Hillsborough, New Jersey 08844. Borough of Manville Maps available for inspection at the Manville Borough Municipal Building, 325 North Main Street, Manville, New Jersey. Send comments to The Honorable Angelo Corradino, Mayor of the Borough of Manville, 325 North Main Street, Manville, New Jersey 08835. Borough of Somerville Maps available for inspection at the Somerville Borough Hall, 25 West End Avenue, Somerville, New Jersey. Send comments to The Honorable Brian G. Gallagher, 25 West End Avenue, Somerville, New Jersey 08876. Township of Warren Maps available for inspection at the Warren Township Engineering Department, 46 Mountain Boulevard, Warren, New Jersey. Send comments to The Honorable Carolyn Garafola, Mayor of the Township of Warren, 46 Mountain Boulevard, Warren, New Jersey 07059. Clinton County, New York (All Jurisdictions) AuSable River Approximately 2.2 miles upstream of Lower Road Bridge None +491 Town of Ausable, Town of Black Brook. At the confluence with West Branch AuSable River +549 +550 Fern Lake The entire shoreline None +1,225 Town of Black Brook. Salmon River Approximately 2,750 feet upstream of Fox Farm Road None +306 Town of Peru. Approximately 1.2 miles upstream of Conners Road None +585 Saranac River Approximately 5,100 feet upstream of Ore Bed Road None +1,090 Town of Black Brook. Approximately 170 feet upstream of Union Falls Road None +1,414 West Branch At the confluence with AuSable River +551 +550 Town of Black Brook. AuSable River Approximately 170 feet upstream of the confluence with AuSable River +552 +551 * National Geodetic Vertical Datum. # Depth in feet above ground. + North American Vertical Datum. ADDRESSES Town of Ausable Maps are available for inspection at the Ausable Town Office, 111 Ausable Street, Keeseville, New York. Send comments to Ms. Sandra Senecal, Ausable Town Supervisor, 111 Ausable Street, Keeseville, New York 12944. Town of Black Brook Maps are available for inspection at the Black Brook Town Office, 18 North Main Street, Ausable Forks, New York. Send comments to Mr. Ricky Nolan, Black Brook Town Supervisor, P.O. Box 715, Ausable Forks, New York 12912. Town of Peru Maps are available for inspection at the Peru Town Office, 3036 Main Street, Peru, New York. Send comments to Mr. Donald E. Covel, Peru Town Supervisor, P.O. Box 596, Peru, New York 12792-0596. Gaston County, North Carolina and Incorporated Areas Blackwood Creek At the confluence with Crowders Creek +669 +662 Gaston County (Unincorporated Areas), City of Gastonia. Approximately 0.9 mile upstream of the confluence with Crowders Creek +674 +673 Muddy Fork Approximately 700 feet downstream of the Cleveland/Gaston County boundary None +823 City of Cherryville, Gaston County (Unincorporated Areas). Approximately 0.6 mile upstream of the Cleveland/Gaston County boundary None +851 Tributary B At the confluence with Tributary A None +719 Gaston County (Unincorporated Areas), City of Gastonia. Approximately 230 feet upstream of the confluence with Tributary B-1 None +784 * National Geodetic Vertical Datum. # Depth in feet above ground. + North American Vertical Datum. ADDRESSES Gaston County (Unincorporated Areas) Maps are available for inspection at Gaston County Administration Office, 128 West Main Street, Gastonia, North Carolina. Send comments to Mr. Jan Winters, Gaston County Manager, 128 West Main Street, Gastonia, North Carolina 28053. City of Cherryville Maps are available for inspection at Cherryville City Hall, 116 South Mountain Street, Cherryville, North Carolina. Send comments to The Honorable Bob Austell, Mayor of the City of Cherryville, 116 South Mountain Street, Cherryville, North Carolina 28021. City of Gastonia Maps are available for inspection at the City of Gastonia Engineering Department, 150 South York Street, Gastonia, North Carolina. Send comments to The Honorable Jennifer Stulz, Mayor of the City of Gastonia, P.O. Box 1748, Gastonia, North Carolina 28053. Windham County, Vermont (All Jurisdictions) Broad Brook At upstream side of State Route 142 None +229 Town of Vernon. Connecticut River Approximately 0.81 mile upstream of Vernon Dam +226 +227 Village of Bellows Falls, Town of Brattleboro, Town of Dummerston, Town of Putney, Town of Rockingham, Town of Vernon, Town of Westminster. Approximately 7.42 miles upstream of Bellows Falls Dam +306 +305 Saxtons River At the confluence with the Connecticut River None +257 Town of Athens, Village of Bellows Falls, Town of Grafton, Town of Westminster. Approximately 1,950 feet upstream of the confluence of Weaver Brook None +590 West River At the confluence with the Connecticut River +235 +232 Town of Brattleboro, Town of Brookline, Town of Dummerston, Town of Jamaica. Upstream side of Ball Mountain Dam None +1,020 * National Geodetic Vertical Datum. # Depth in feet above ground. + North American Vertical Datum. ADDRESSES Village of Bellows Falls Maps are available for inspection at the Bellows Falls Village Hall, 7 Square, 3rd Floor, Bellows Falls, Vermont. Send comments to Mr. John B. Schempf, Village of Bellows Falls Municipal Manager, P.O. Box 370, Bellows Falls, Vermont 05101. Town of Brattleboro Maps are available for inspection at the Brattleboro Planning Services Department, 230 Main Street, Suite 202, Brattleboro, Vermont. Send comments to Mr. Stephen A. Steidle, Chairman of the Town of Brattleboro Board of Selectmen, 230 Main Street, Suite 208, Brattleboro, Vermont 05301. Town of Brookline Maps are available for inspection at the Brookline Town Office, 736 Grassy Brook Road, Brookline, Vermont. Send comments to Ms. Joyce Meehl, Chairperson for the Town of Brookline Board of Selectmen, P.O. Box 403, Newfane, Vermont 05345. Town of Dummerston Maps are available for inspection at the Dummerston Town Hall, 1523 Middle Road, East Dummerston, Vermont. Send comments to Ms. Cynthia Jerome, Chairperson for the Town of Dummerston Board of Selectmen, 1523 Middle Road, East Dummerston, Vermont 05346. Town of Putney Maps are available for inspection at the Putney Town Hall, 127 Main Street, Putney, Vermont. Send comments to Mr. Christopher Ryan, Putney Town Manager and Zoning Administrator, P.O. Box 233, Putney, Vermont 05346. Town of Vernon Maps are available for inspection at the Vernon Town Office, 567 Governor Hunt Road, Vernon, Vermont. Send comments to Mr. Peter Deyo, Chairman of the Town of Vernon Board of Selectmen, 567 Governor Hunt Road, Vernon, Vermont 05354. Town of Westminster Maps are available for inspection at the Westminster Town Hall, 3651 U.S. Route 5, Westminster, Vermont. Send comments to Mr. Paul Harlow, Chairman of the Town of Westminster Board of Selectmen, P.O. Box 147, Westminster, Vermont 05158. Towns of Weathersfield and Windsor, Windsor County, Vermont Connecticut River Approximately 1.91 miles downstream of confluence of the Black River +306 +305 Town of Harland, Town of Springfield, Town of Weathersfield, Town of Windsor. Approximately 2.27 miles upstream of confluence of Lulls Brook +334 +335 * National Geodetic Vertical Datum. # Depth in feet above ground. + North American Vertical Datum. ADDRESSES Town of Weathersfield Maps are available for inspection at the Town of Weathersfield, Martin Memorial Hall, 5259 Route 5, Ascutney, Vermont. Send comments to Mr. Lawrence Melen, Weathersfield Town Manager, P.O. Box 550, Ascutney, Vermont 05030-0550. Town of Windsor Maps available for inspection at the Windsor Town Office, 29 Union Street, Windsor, Vermont. Send comments to Mr. Donald Howard, Windsor Town Administrator, 29 Union Street, Windsor, Vermont 05089. (Catalog of Federal Domestic Assistance No. 83.100, “Flood Insurance.”) Dated: January 12, 2007. David I. Maurstad, Director, Mitigation Division, Federal Emergency Management Agency, Department of Homeland Security. [FR Doc. E7-887 Filed 1-22-07; 8:45 am] BILLING CODE 9110-12-P DEPARTMENT OF TRANSPORTATION 49 CFR Part 39 [Docket OST 2007 26829] RIN 2105-AB87 Transportation for Individuals With Disabilities: Passenger Vessels AGENCY: Department of Transportation, Office of the Secretary. ACTION: Notice of proposed rulemaking. SUMMARY: The Department is proposing to issue a new Americans with Disabilities Act
(ADA)rule to ensure nondiscrimination on the basis of disability by passenger vessels. This notice of proposed rulemaking
(NPRM)concerns service and policy issues. Issues concerning physical accessibility standards will be addressed at a later time, in conjunction with proposed passenger vessel accessibility guidelines drafted by the Access Board. *Comment Closing Date:* Comments should be submitted by April 23, 2007. Late-filed comments will be considered to the extent practicable. ADDRESSES: You may submit comments identified by the docket number [OST 2007-26829] by any of the following methods: • Web site: *http://dms.dot.gov* . Follow the instructions for submitting comments on the DOT electronic docket site. • *Federal e-Rulemaking Portal:* *http://www.regulations.gov* . Follow the instructions for submitting comments. • *Fax:*
(202)493-2251. • *Mail:* Docket Management System; U.S. Department of Transportation, 400 Seventh Street, SW., Nassif Building, Room PL-401, Washington, DC 20590-0001. • *Hand Delivery:* To the Docket Management System; Room PL-401 on the plaza level of the Nassif Building, 400 Seventh Street, SW., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. *Instructions:* You must include the agency name and docket number [OST-2007-26829] or the Regulatory Identification Number
(RIN)for this rulemaking at the beginning of your comment. Note that all comments received will be posted without change to *http://dms.dot.gov* , including any personal information provided. *Docket:* You may view the public docket through the Internet at *http://dms.dot.gov* or in person at the Docket Management System office at the above address. FOR FURTHER INFORMATION CONTACT: Robert C. Ashby, Deputy Assistant General Counsel for Regulation and Enforcement, Department of Transportation, 400 7th Street, SW., Room 10424, Washington, DC 20590-0001.
(202)366-9306 (voice);
(202)755-7687 (TDD); *bob.ashby@dot.gov* (e-mail). SUPPLEMENTARY INFORMATION: The Department of Transportation has issued rules concerning nondiscrimination on the basis of disability for almost every mode of passenger transportation, including public transportation (bus, subway, commuter rail), over-the-road buses, intercity rail, and air transportation. The only mode on which the Department has yet to propose rules is transportation by passenger vessels. With this NPRM, the Department is beginning the process of filling this remaining gap in our coverage of transportation for individuals with disabilities. Background When the Department issued its first Americans with Disabilities Act
(ADA)rules in 1991, we explicitly asserted coverage over passenger vessels. The Department reserved action on passenger vessels in the regulatory text of this final rule, and we made the following statements on the subject in the preamble (56 FR 45599-45560; September 6, 1991): Ferries and passenger vessels operated by public entities are covered by the ADA, and subject at this time to DOJ Title II requirements as well as § 37.5 of this Part * * *. We anticipate further rulemaking to create appropriate requirements for passenger vessels * * *. The reason for this action is that, at the present time, the Department lacks sufficient information to determine what are reasonable accessibility requirements for various kinds of passenger vessels. We note that the DOJ has determined that passenger vessels encompassing places of public accommodation (e.g., cruise ships, floating restaurants) are subject to the general nondiscrimination and policies and practices portions of its Title III rule (Subparts B and C of 28 CFR Part 36). The Department of Transportation anticipates working with the Access Board and DOJ on further rulemaking to define requirements for passenger vessels * * *. The Department does want to make clear its view that the ADA does cover passenger vessels, including ferries, excursion vessels, sightseeing vessels, floating restaurants, cruise ships, and others. Cruise ships are a particularly interesting example of vessels subject to ADA coverage. Cruise ships are a unique mode of transportation. Cruise ships are self-contained floating communities. In addition to transporting passengers, cruise ships house, feed, and entertain passengers and thus take on aspects of public accommodations. Therefore cruise ships appear to be a hybrid of a transportation service and a public accommodation. As noted above, DOJ covers cruise ships as public accommodations under its Title III rules. In addition to being public accommodations, cruise ships clearly are within the scope of a “specified public transportation service.” The ADA prohibits discrimination in the full and equal enjoyment of specified public transportation services provided by a private entity that is primarily engaged in the business of transporting people and whose operations affect commerce (§ 304(a)). “Specified public transportation” is defined by § 301(10) as “transportation by bus, rail, or any other conveyance (other than by aircraft) that provides the general public with general or special service (including charter service) on a regular and continuing basis.” Cruise ships easily meet the definition of “specified public transportation.” Cruise ships are used almost exclusively for transporting passengers and no one doubts that their operations affect commerce. Cruise ships operate according to set schedules or for charter and their services are offered to the general public. Finally, despite some seasonal variations, their services are offered on a regular and continuing basis. Virtually all cruise ships serving U.S. ports are foreign-flag vessels. International law clearly allows the U.S. to exercise jurisdiction over foreign-flag vessels while they are in U.S. ports, subject to treaty obligations. A state has complete sovereignty over its internal waters, including ports. Therefore, once a commercial ship voluntarily enters a port, it becomes subject to the jurisdiction of the coastal state. In addition, a state may condition the entry of a foreign ship into its internal waters or ports on compliance with its laws and regulations. The United States thus appears to have jurisdiction to apply ADA requirements to foreign-flag cruise ships that call in U.S. ports. The U.S. Supreme Court recently affirmed the Department's long-held view that the ADA covers passenger vessels, specifically including foreign-flag cruise ships. In *Spector et al.* v. *Norwegian Cruise Lines* , 545 U.S. 119 (2005), the Court held that cruise ships are “public accommodations” that provide “specified public transportation” within the meaning of the ADA. The Court said that, while there may be some limitations on the coverage of the ADA to matters purely concerning the internal affairs of a foreign-flag vessel, matters concerning the ship operators' policies and conditions relating to transportation of passengers with disabilities ( *e.g.* , higher fares or surcharges for disabled passengers, waivers of medical liability, requirements for attendants) had nothing to do with a ship's internal affairs. Such matters, then, are clearly subject to ADA jurisdiction. It is issues of this kind that are the focus of this NPRM. The Access Board has been working for some time on drafting accessibility guidelines for passenger vessels. On November 26, 2004, the Access Board published for comment a notice of availability of draft guidelines for larger passenger vessels with a capacity of over 150 passengers or overnight accommodations for over 49 passengers. Since that time, the Access Board has been reviewing comments it received and planning work on a Regulatory Assessment for vessel guidelines. On July 7, 2006, the Access Board issued a second notice of availability asking for comments on a revised draft of vessel guidelines. Following the review of comments on that notice, the Access Board, in cooperation with the Department of Transportation, would issue an NPRM and Regulatory Assessment concerning physical accessibility requirements for larger passenger vessels. As we envision it, the final rule resulting from such a future NPRM would ultimately be joined with a final rule resulting from the current proposed rule in a single, comprehensive passenger vessel ADA rule. On November 29, 2004, the Department published an advance notice of proposed rulemaking (ANPRM) asking questions about the shape of future ADA requirements for passenger vessels (69 FR 69247). The Department received 43 comments to the ANPRM. Most of these comments concerned the Access Board's draft guidelines and physical accessibility issues relating to existing and new vessels, and some of them concerned physical accessibility issues specific to very small vessels. The Department is retaining these comments and will consider them in context of the continuing work on the Access Board's draft vessel guidelines and the future NPRM that would propose to incorporate those guidelines in DOT rules. The only comment that concerned the issues included in this NPRM was from the International Council of Cruise Lines (ICCL), a trade association for entities in the cruise industry. ICCL recommended that rules exempt transfers of persons from larger vessels to tenders; recognize the flexibility of cabin configurations; exclude from coverage shore excursions provided by third-party-vendors, particularly in foreign countries; have eligibility criteria and direct threat provisions that allow operators to establish policies that will avoid safety risks; permit requirements for personal attendants; and permit limitations on the transportation of service animals. The Department will discuss these comments in context of the individual sections of the proposed rule. Section-by-Section Analysis § 39.1 What is the purpose of this part? This section briefly states the nondiscrimination-related purposes of the rule and specifies that nondiscrimination requirements apply to operators of foreign-flag as well as U.S. vessels. § 39.3 What do the terms in this rule mean? This section proposes definitions of terms in this rule. Many of the definitions are based on parallel definitions in the Department's ADA and Air Carrier Access Act
(ACAA)regulations or Department of Justice rules, adapted to the passenger vessel context. This preamble discussion focuses on terms that are specific to the passenger vessel context. Other terms would have the same meanings as they do in other DOT disability rules. Because this NPRM does not propose physical accessibility requirements for vessels, the definition of “accessible” will be fleshed out with proposed standards based on Access Board guidelines in a future rulemaking. The definition of “direct threat,” drawn from Department of Justice regulations, concerns only threats to the health and safety *of others* . Something that may threaten only the health or safety of a passenger with a disability by definition cannot be a direct threat. In addition to vessels, “facilities” include landside facilities that a vessel operator owns, leases, or controls in the U.S. (including its territories, possessions, and commonwealths). A passenger vessel operator
(PVO)would be viewed as controlling a facility, even if it did not own or lease it, if the facility owner, through a contract or other arrangement, delegated authority over use of the facility to the passenger vessel operator during those times in which the vessel was at the facility. Facilities in these three categories would be covered directly by Part 39. The Department seeks comment on how responsibilities should be allocated when there are multiple PVOs who operate at a given landside facility or who only use the facility infrequently. The Department realizes that entities other than PVOs, such as municipalities or other private businesses, may own, lease, or control landside facilities that passenger vessels use. The obligations of these entities would be controlled by Titles II and III of the ADA and, in some cases, by section 504 of the Rehabilitation Act of 1973. We envision the relationship between the facility owner/controller and the PVO to be analogous to other situations in which entities subject to different disability access rules share responsibility ( *e.g.* , public entity landlord subject to Title II leases property to a private entity subject to Title III). We seek comment on whether landside facility-specific language should be added to the Department's other ADA or section 504 rules. The NPRM does not propose making this requirement applicable to facilities located outside the U.S. However, we seek comment on whether the final rule should apply to facilities outside the U.S. if a PVO (as distinct from another foreign entity) owns, leases, or controls the facility. The definition of “historic vessel” is also one that is likely to become more significant when future rulemakings add physical accessibility standards to Part 39. Following practice in other portions of the ADA, it is likely that historic vessels ( *e.g.* , the USS *Constellation* in Baltimore harbor) would be exempted from some accessibility requirements. “New,” “existing,” and “used” passenger vessel are also terms that will be of greater importance once physical accessibility standards are in place. They are based on new and used vehicle definitions in the Department's ADA rules for surface transportation modes. With respect to the definition of “new passenger vessel,” which will be used in connection with vessel standards in Subpart E when they are added to the regulation, we seek comment on transition rules. That is, at what point in the procurement, design, construction, and delivery of a vessel should requirements for new vessels attach? “Operates” means the provision of transportation or other service by any public or private entity on a passenger vessel. Importantly, it also includes the provision of transportation or other service by another party having a contractual or other arrangement or relationship with the entity involved. As in other parts of the Department's accessibility rules, a party can contract out its functions, but cannot contract away its responsibilities. By “other services,” we mean activities that take place on a vessel other than simply going from Point A to Point B ( *e.g.* , food service, recreation, entertainment, gambling). This section would also cover situations in which a vessel makes a round trip from Point A to Point A, like some dinner, excursion, and gambling vessels do. “Passenger vessel” is meant to be a broadly encompassing term for any boat, ship, or other craft that takes on members of the public for hire or other activities conducted as a part of the vessel operators normal operations (which could include promotional activities involving use of a vessel by members of the public for which a fare is not charged, free shuttle or ferry service). The only exception is for boats or other craft that are rented or leased to consumers and which the consumers themselves (as distinct from the passenger vessel operator and its personnel) operate. The Department seeks comment on whether there are any additional situations that the rule should cover ( *e.g.* , the PVO or an organization to which the PVO makes the vessel available provides a charitable or promotional excursion for which no fee is charged). The Department also seeks comment on whether there should be exceptions or different provisions for vessels that are not primarily designed or used as passenger vessels, but may carry passengers for hire on certain occasions ( *e.g.* , supply vessels, crew boats, school training or sailing vessels, research vessels carrying students). In some cases, such as certain on-the-water gambling casinos, museums, or restaurants, an activity takes place on a structure that floats but is permanently anchored or tethered to a dock or other shore facility. On one hand, because it floats on the water, such a structure could be regarded as a vessel covered by this rule. On the other hand, because it never actually goes anywhere, it could be regarded as a facility, like an on-shore building, that is more appropriately covered by Department of Justice rules. We seek comment on this matter. The “passenger vessel operator”
(PVO)is a term that includes both owners and operators of a passenger vessel. A PVO may be either a public or a private entity. Sometimes, ownership of vessels can be complex, with two or more different parties involved, and yet another party responsible for the day-to-day operation of the vessel. In such situations, all the parties involved would be jointly and severally responsible for compliance with these rules. For the most part, “passenger with a disability” and “qualified individual with a disability” have the same meaning for purposes of the proposed rule. There could be situations in which a qualified individual with a disability may not actually be a passenger, or in which someone is seeking to perform functions on behalf of a person with a disability. The “passenger with a disability” term includes both situations in which someone buys a ticket to travel on a vessel and situations ( *e.g.* , a gambling boat) in which members of the public go on board, without a ticket, to use the services provided on the vessel, regardless of whether the vessel leaves its dock or mooring. “Terminal” would be defined broadly, meaning any property or facilities adjacent to the means of boarding a vessel that passengers use to get to the vessel. A terminal, in this sense, can be a large complex, a building, or a very simple facility. Importantly, terminals are covered under Part 39 only to the extent that the PVO owns or leases the terminal or exercises control over its selection, design, construction, or alteration ( *e.g.* , POV <sup>[A1]</sup> selects site for construction of new facility; or PVO has choice of docking at existing accessible or inaccessible facility). As noted in the discussion of “facility,” the Department seeks comment on whether Part 39 should apply to a terminal located outside the U.S. if the PVO is involved in one of these ways. If the PVO does none of these things, the terminal would not in any circumstance be covered under Part 39, though other parts of the ADA and section 504 of the Rehabilitation Act of 1973, as amended, may well apply to terminals located in the U.S. We also note that activities that a PVO itself conducts, regardless of the facility in which they are conducted, would be expected to be available to persons with disabilities. In other transportation contexts, there has been considerable discussion of whether the long-standing definition of “wheelchair” remains adequate, in light of the development and use of mobility devices that may not fit within the definition. We seek comment on this question in the context of passenger vessels. Should there be a definition that specifically acknowledges mobility devices that may not literally be “wheelchairs,” or should a more inclusive term be developed? § 39.5 To whom do the provisions of this part apply? The Department proposes that the provisions of this part apply to all passenger vessels, regardless of size. There are two major exceptions to this general coverage. First, while all U.S.-flagged vessels would be covered, coverage of foreign-flag vessels would be limited to those that pick up or discharge passengers in the U.S. For example, suppose a foreign-flag cruise PVO operates two ships. One of them sails only among ports in Europe. Another picks up passengers in Miami and cruises to several Caribbean ports. The latter would be covered and the former would not. The Department seeks comment on a situation that may occur, in which tickets are sold to U.S. passengers for a combined trip that includes transportation to a non-U.S. port where they board a ship. For example, suppose Grand Fenwick Cruise Lines sells a package to U.S. passengers including air fare from New York to the Bahamas, where passengers board the S.S. *Grand Duchess Gloriana* for a Caribbean cruise; should the ship transportation be covered for purposes of Part 39 nondiscrimination rules? The second exception concerns the future vessel accessibility standards. The NPRM reserves paragraph (c), which would state the scope of the applicability of these standards. The Department notes that the July 2006 draft Access Board vessel <sup>[A2]</sup> would limit their application vessels permitted to carry over 150 passengers or over 49 overnight passenger capacity categories, as well as tenders with a capacity of 59 or more and all ferries. The Department currently anticipates following the Access Board's final guidelines, when they are issued, with respect to coverage. The Department also seeks comment on whether there should be any vessel size or capacity limits on any of the specific nondiscrimination provisions that are proposed in this NPRM with respect to subjects other than vessel accessibility standards. § 39.7 What other authorities concerning nondiscrimination on the basis of disability apply to owners and operators of passenger vessels? This section simply points out that recipients of Federal financial assistance ( *e.g.* , some public ferry operators) are, in addition to Part 39, subject to section 504 of the Rehabilitation Act and DOT implementing rules. Department of Justice
(DOJ)ADA regulations, as applicable, also cover PVOs. § 39.9 What may a PVO of a foreign-flag vessel do if it believes that a provision of a foreign nation's law prohibits compliance with a provision of this part? § 39.11 How may a PVO obtain approval to use an equivalent facilitation? These sections provide means by which PVOs may obtain DOT authorization to do something different from what these regulations would require. Section 39.9, which parallels language in the Department's proposed Air Carrier Access Act
(ACAA)rules for foreign carriers, provides a waiver mechanism for situations in which a PVO for a foreign-flag vessel believes that a binding legal requirement of a foreign nation (or of an international agreement) precludes compliance with a requirement of Part 39. This provision concerns binding legal requirements, not guidance or codes of suggested practices. It concerns situations in which such a binding legal requirement actually precludes compliance with a Part 39 provision ( *e.g.* , Part 39 says “You must do X,” while a binding foreign legal requirement says “You must not do X”), as opposed to a situation where foreign law authorizes a practice that differs from a Part 39 requirement ( *e.g.* , Part 39 says “You must do Y,” while a foreign law says “You may do Z”). In a situation where the Department grants a waiver, the Department would look to the PVO for a reasonable alternative means of achieving the purpose of the waived provision. To avoid placing PVOs in a situation in which they potentially were required to comply with contradictory legal requirements, the NPRM proposes that PVOs seeking a waiver would have 90 days from the publication of the final rule to file a waiver request. If the PVO filed a complete waiver request within that period, it could continue to implement policies that it believes are consistent with the foreign law in question pending the Department's decision on the waiver request. Section 39.11, on the other hand, concerns a potentially wider range of situations in which a PVO applies to the Department for authorization to provide a different means of compliance with a requirement of the DOT rules than the rules themselves specify. Equivalent facilitations can apply to the details of physical accessibility standards, when they become part of the rule, but could also apply to policy and administrative matters covered by the rule. It is important to note that to be considered an equivalent facilitation, the different means of compliance must provide equal or greater accessibility than that required by the regulatory text. § 39.13 When must PVOs comply with the provisions of this part? As a general matter, PVOs would have to begin to comply with the provisions of this rule as soon as the rule becomes effective. There is no evident reason why PVOs should need a lengthy phase-in period to comply with requirements pertaining to denials of transportation on the basis of disability, extra or special charges, personal or safety assistants, advance notice, waivers of liability, etc. The Department would hope and expect that most PVOs are already acting in ways that are in compliance with these nondiscrimination policy and administrative practice requirements. If not, then this NPRM should put PVOs on notice that changes in their policies may be necessary in the near future. There are some provisions of the proposed rule concerning which it would be reasonable for PVOs to have a longer phase-in period, however. Specific sections on such matters as modifications to terminals and other landside facilities and training for personnel have proposed compliance dates intended to give PVOs a reasonable time to meet requirements. The Department seeks comment on these proposed compliance dates, as well as on whether there are other provisions on which PVOs would need additional time to comply. § 39.21 What is the general nondiscrimination requirement of this part? The provisions of this section are parallel to the general nondiscrimination requirements in the Department's other disability-related rules. We would call attention particularly to paragraph (b), which would require modification of PVOs' otherwise acceptable general policies where doing so is necessary to accommodate the needs of a particular individual or category of individuals with a disability. Such modification is required unless it would be unduly burdensome or require a fundamental alteration in the nature of the PVO's services, programs, or activities. § 39.23 What are the requirements concerning contractors to owners and operators of passenger vessels? As noted above, contractors and other persons whom the PVO uses to provide services to passengers “stand in the shoes” of the PVO with respect to the requirements of this rule. The PVO must ensure, through provisions in the contracts or other agreements with such third parties, that the third parties comply with applicable requirements. We seek comment on whether, if at all, contractors outside the United States should be covered by this requirement. All new contracts and other agreements must have this assurance language. The Department seeks comment on whether the rule should require the addition of assurance language to existing contracts and agreements, and, if so, what the compliance period for such additions should be. Since PVOs cannot contract away their responsibilities, PVOs remain responsible for the third parties' actions. This would be true, in the Department's view, even with respect to actions of third parties where the PVO's agreements with the third parties did not yet include assurance language. § 39.25 May PVOs limit the numbers of passengers with a disability on a passenger vessel? The Department views any policy limiting the number on passengers with a disability on a vessel as discriminatory on its face. With respect to the concern expressed by ICCL about large groups of passengers with a disability traveling together, we believe that the provision of § 39.35 permitting PVOs to ask for advance notice in this situation ( *e.g.* , so as to be able to make the needed reconfigurations of the flexible space in overnight accommodations that ICCL's comment mentions) should be helpful. § 39.27 May PVOs refuse to provide transportation or use of a passenger vessel on the basis of disability? The Department views any policy or action prohibiting a person with a disability from being transported on or otherwise using a passenger vessel as discriminatory on its face. If a PVO says to a person, literally or in effect, “you are a person with a disability, therefore stay off my vessel,” the PVO would violate this rule. The Department recognizes that some disabilities may make other passengers uncomfortable. That is not a justifiable reason to deny access to the vessel to persons with these disabilities (see paragraph (b)). Only if there is a genuine safety issue, meeting the stringent direct threat criteria outlined in paragraph (c), would the PVO be justified in excluding a person because the person has a disability. Even in that case, the PVO would have to provide a written explanation to the person within 10 days of the denial (paragraph (d)). The Department recognizes that, particularly prior to the adoption of physical accessibility standards, some vessels will not have accommodations that will permit persons with some disabilities to travel on or to obtain some services on the vessels. For example, an older vessel might not have any overnight cabins of a size that could accommodate a person using a power wheelchair, or might have a dining area that is on a deck which can be accessed only by using steps. The Department would not, in such a situation, regard a PVO's statement to a passenger about the lack of adequate physical accommodations as equivalent to a policy denying access on the basis of disability. § 39.29 May PVOs limit access to transportation on or use of a vessel on the basis that a passenger has a communicable disease or other medical condition? § 39.31 May PVOs require a passenger with a disability to provide a medical certificate? These related provisions are intended to limit PVOs' discretion to impose requirements or restrictions on passengers on medical grounds. Most disabilities are not medical conditions: A person is not ill because he or she cannot see, hear, or walk, and applying a medical model to many disabilities is inappropriate. On the other hand, people with a variety of medical conditions ( *e.g.* , heart disease) may have at least temporary disabilities. If there is reasonable doubt that a passenger with a medical condition can complete a given trip or use a vessel without requiring extraordinary medical assistance, then this rule would permit the PVO to require a medical certificate from the individual. In applying this requirement, the Department believes it is reasonable for the PVO to take into account the length of the passenger's stay aboard the vessel. With respect to communicable diseases, the PVO cannot deny or restrict transportation on or use of a passenger vessel on the basis that the passenger has a communicable disease, unless the PVO makes a direct threat determination. In the communicable disease area, the Department believes that PVOs should consider two factors. One is the severity of the consequences of a disease; the other is whether the disease can readily be communicated by casual contact. Only if a disease has severe consequences to the health of other persons and is readily communicable by casual contact could a PVO legitimately determine that there is a direct threat. For example, HIV/AIDS has severe consequences, but is not readily communicable by casual contact. The common cold is readily communicable by casual contact but typically does not have severe health consequences. Consequently, having a cold or having AIDS would not be a basis on which a PVO could limit a person's transportation on or use of a vessel. Probably the best recent example of a disease that meets both criteria is Severe Acute Respiratory Syndrome (SARS), and, in the future, a readily human-to-human transmissible avian flu pandemic might well qualify. PVOs could legitimately take into account determinations by public health authorities about the travel of persons with a certain disease ( *e.g.* , if the Centers for Disease Control or World Health Organization issued a finding that persons with a certain disease or symptoms should not travel). In any case in which a medical certificate may be required or a limitation on a passenger's travel be imposed, the limitation should be the minimum needed to deal with the medical issue or direct threat to the health of others. For example, the PVO would not be authorized to deny transportation to an individual if a less drastic alternative, such as the use of a personal assistant or the passenger's use of medical measures that would mitigate the transmission of an illness is available. If a PVO refuses transportation to a passenger with a disability on grounds related to a medical condition, the NPRM proposes that the PVO would have to permit the passenger to travel or use the vessel at any time within a year at the same price as the original trip or, at the passenger's discretion, provide a refund. The Department seeks comment on whether and how to apply this concept to situations in which an equivalent trip is not available within a year ( *e.g.* , Grand Fenwick Cruise Lines makes only one trip to Tierra del Fuego every three years, or the S.S. Grand Duchess Gloriana's trips are all fully booked for the next year). The Department also seeks comment on how, if at all, the availability of trip insurance to the individual passenger should be related to this proposed provision. § 39.33 May PVOs require a passenger with a disability to provide advance notice that he or she is traveling on or using a passenger vessel? § 39.35 May PVOs require a passenger with a disability to provide advance notice in order to obtain certain services in connection with transportation on or use of a passenger vessel? In these related sections, the Department is saying, first, that it is never appropriate for a PVO to require a person to provide advance notice that he or she is coming, just because he or she has a disability. The PVO's nondiscriminatory policies and practices should be in place, ready to deal with whoever shows up. On the other hand, there may be specific accommodations for which provision of advance notice is needed. One that seems reasonable is when a large number of people with a disability plan to travel as a group. The NPRM uses the ACAA standard of a group of 10 or more disabled passengers traveling as a group. We seek comment on whether this concept should be refined to recognize the possibility that some groups of disabled passengers traveling together may not need any special accommodations. In such a case, is the advance notice provision advisable? A second instance where advance notice could be helpful concerns a request for an accessible overnight cabin. The Department's proposal on this subject is intended to grapple with the reported problem of nondisabled travelers reserving an accessible cabin because it is roomier, thus denying its availability to a disabled passenger who may subsequently seek the accommodation. Under the proposal, everyone reserving an accessible cabin would be informed that, if a passenger with a disability made a reservation at least 72 hours before the vessel's scheduled departure and requested an accessible cabin, any nondisabled person who had previously reserved the cabin would be moved to another cabin, if one were available. The NPRM would not require any passenger to be bumped from a voyage as a result, only reassigned to a different cabin. Obviously, the operation of this provision would depend on self-identification by the passenger with a disability of his or her need for the accessible cabin. The Department seeks comment on whether the rule should specify in more detail the kinds of disabilities that would trigger this provision ( *e.g.* , should the provision be limited to persons with mobility impairments?) or whether the PVO should be permitted, or required, to seek documentation of a disability from a passenger seeking to reserve such an accommodation. We also seek suggestions for any alternative means of addressing this issue. We recognize that, especially on some cruise ships, it is commonplace for travelers to reserve cabins months in advance. It is also commonplace for whole voyages to be sold out months in advance. We seek comment, thus, on whether a passenger with a disability who requested an accessible cabin 72 hours before departure could appropriately bump a nondisabled passenger from a cabin reserved months ahead of time. Similarly, we seek comment on whether a deadline for requesting an accessible cabin should be 72 hours or another fixed time before departure or, alternatively, based on when passengers in general reserve their cabins. (If the latter, for example, an accessible cabin might have to be requested before half of all cabins are reserved.) Additionally, we seek comment on whether, as we do in the ADA rule for over-the-road buses, we should provide that any cut-off date for reservations in general should also be applied to requests for an accessible cabin. The Department recognizes that, pending the development of passenger vessel physical accessibility standards, even new vessels are not required to have a particular number of accessible cabins. This provision would apply to the accessible cabins that now exist, as well as any others that may become available in the future. We also recognize that there could be situations in which an accessible room would not be available to a passenger with a disability because another passenger with a disability had already reserved the room. Other than treating such situations as a “first-come first-served” manner, do commenters have any suggestions for resolving such a situation? The Department also seeks comment on whether 72 hours would be a reasonable amount of advance notice in these situations and on whether there are other services for which an advance notice requirement would be reasonable. There could be situations in which a similar principle could arguably apply to other shipboard activities. For example, some cruise ships may assign seats for dinner. If a passenger with a disability was unable, because of barriers in the dining area, to get readily to his or her assigned seat, could it be viewed as a reasonable modification of the PVO's seating policy to shift dining table assignments of other passengers to provide accessibility to a dining table? If so, taking into account any disruption of the operator's seating plans or of the other passengers' seating arrangements, would a request for an accessible table have to be made a specified number of hours before departure? The Department seeks comment on this or similar issues involving on-board activities. § 39.37 May PVOs require a passenger with a disability to travel with a personal or safety assistant? The Department regards requiring a passenger with a disability to travel with another person, just because that person has a disability, as discriminatory on its face. Such a requirement is not only an affront to the independence and dignity of the passenger, but may sometimes make travel cost-prohibitive. On the other hand, there can be situations in which traveling with another person as a safety assistant is essential for safety purposes. Paragraph
(b)spells out three situations in which it would be justifiable to impose a requirement for a safety assistant. These situations are drawn from the similar provision of the Department's ACAA rule, and the Department seeks comment on any other situations in vessel contexts where such a requirement could be justified. As ICCL's comment noted, because some passenger voyages are much longer than airplane flights, there may be situations in which a personal assistant is necessary (the ACAA rule never permits a requirement for personal assistants, as distinct from persons needed to assist with an emergency evacuation, in air travel). Consequently, the Department proposes that if a passenger with a disability needs a personal assistant to help perform key personal tasks, such as eating, toileting, and dressing, and the passenger's use of the vessel will be lengthy enough so that the passenger will need to perform these tasks, the PVO may require the passenger with a disability to have a personal assistant. For shorter voyages akin in length to airplane flights, the PVO could not impose such a requirement. However, for a longer voyage ( *e.g.* , a multi-day cruise), the PVO could do so. The Department recognizes that there can be situations in which a passenger and a PVO disagree about whether a safety or personal assistant is necessary. In these situations, the proposed rule contemplates that the PVO would have the last word, and could require the attendant over the passenger's objections. However, in such a situation, the rule would require the PVO to put its money where its mouth is, and not charge for the transportation or use of the vessel by the assistant who the passenger was involuntarily required to bring along. As under the ACAA rule (where a similar provision has been in effect since 1990 without causing significant disruptions), the PVO could designate a member of its own staff or a passenger volunteer as the assistant, in order to deter any potential abuse by a passenger who would, for example, unreasonably object to the use of an assistant in order to secure free transportation for a friend or family member. § 39.39 May PVOs impose special charges on passengers with a disability for providing services and accommodations required by this rule? Price discrimination is forbidden. PVOs may not charge higher fares to passengers with disabilities than to other passengers. PVOs cannot impose surcharges on passengers with disabilities, or any sort of extra or special charges for facilities, equipment, accommodations, or services that must be provided to passengers because they have a disability. This prohibition would apply not only to formal charges made by the PVO itself, but to informal charges that PVO personnel might seek to impose or pressure passengers with a disability to pay. For example, if a vessel cannot be boarded by a wheelchair user without assistance ( *e.g.* , because the boarding ramp slope is too steep), it would not be appropriate for vessel personnel who provide boarding assistance to ask, pressure, or imply that the wheelchair users should provide a tip for the assistance. One of the important implications of the prohibition on price discrimination concerns situations in which an accommodation for a person with a disability is available only in a more expensive type or class of service than the passenger requests. For example, suppose a passenger with a disability tries to make a reservation for an inside cabin. However, the only accessible cabins on the vessel are in the more expensive outside cabins with windows. The PVO would have to provide the accessible cabin to the passenger with a disability at the price of the less expensive accommodation he or she had requested. This is consistent with ADA practice in other contexts, such as booking of hotel rooms or sleeping compartments on Amtrak trains. § 39.41 May PVOs impose restrictions on passengers with a disability that they do not impose on other passengers? § 39.43 May PVOs require passengers with a disability to sign waivers or releases? The NPRM would forbid restrictions on passengers with a disability that are not imposed on other passengers, including requirements to sign waivers or releases either for themselves or their assistive devices. The kinds of restrictions these sections address are restrictions created by PVO policy. The Department is aware that, particularly pending the adoption of passenger vessel physical accessibility standards, portions of existing vessels may well be inaccessible to some passengers with a disability. Inaccessibility of this kind would not violate these sections, but an administrative rule declaring certain portions of a vessel off limits to a passenger with a disability would, if that rule did not apply equally to all passengers. § 39.51 What information must PVOs provide to passengers with a disability? The Department recognizes that vessels and facilities will not be equally accessible; that some vessels, ports, services, and facilities may not be usable by persons with some disabilities. This section would require PVOs to inform people with disabilities, accurately and in detail, about what they can expect. What features of a vessel are accessible and what are not? What limitations, if any, are there concerning the ability of a vessel to accommodate persons with a particular disability? At what ports could passengers with a disability expect to be able to get on and off the ship, and by what means? If third parties are making tours and excursions available to passengers, to what extent are these tours accessible to persons with a particular disability? With this information, potential passengers with a disability can make an informed choice about whether seeking transportation on a particular vessel is worth their while. § 39.53 Must information and reservation services of PVOs be accessible to individuals with hearing or vision impairments? This section would apply to information and reservation services made available to consumers in the United States, regardless of the nationality of a PVO or where the personnel or equipment providing the services are themselves based. The first proposed requirement is for TTY service for persons with hearing impairments. The Department is aware that some deaf and hard-of-hearing persons now may use other technologies in preference to TTYs ( *e.g.* , videophones, instant messaging), and we seek comment on how, if at all, this development should be reflected in a final rule. On-line booking services, as well as web sites providing information about passenger vessel availability, schedules, and services, are very important in today's marketplace. Consequently, the Department views it as very important for on-line resources to be available to persons with disabilities. We would view a web site meeting section 508 or World Wide Web Consortium standards as being accessible for this purpose. The regulatory text does not make a specific proposal on this subject, but we seek comment on whether the final rule based on this NPRM, or a future rule incorporating vessel accessibility standards, should include such a requirement. We also seek comment on the costs of requiring Web site accessibility in the passenger vessel industry, the appropriate standards for accessible sites, and the timing and phase-in period appropriate for such a requirement. § 39.55 Must PVOs make copies of this rule available to passengers? The NPRM would propose that PVOs maintain a copy of the rule on each vessel and at each U.S. terminal. The purpose of doing so would be to make the rule readily available for reference in case a question occurred about whether a PVO was acting consistently with its requirements. § 39.57 What is the general requirement for PVOs' communications with passengers? This section states the general effective communication requirement for PVOs. § 39.61 What requirements must PVOs meet concerning the accessibility of terminals and other landside facilities? This section applies to landside facilities that the PVO owns, leases, or controls in the U.S. If the PVO does not own, lease, or control a facility, then the requirements of this section do not apply to it (there may well be situations in which case a public entity or another private entity would own or control the facility, in which the other entity would have its own ADA and/or 504 obligations). In the case of a foreign facility, where ADA or section 504 rules would not apply in their own right, facility accessibility would then become a matter of the law of the country in which the facility is located. As noted in the discussion of the definition of “facility,” the Department seeks comment on whether a PVO covered by this rule should have accessibility obligations for a foreign facility that the PVO itself, as distinct from a separate foreign entity, owns, controls or leases. The rule would make a familiar three-part breakdown of accessibility responsibilities for covered facilities. New facilities must meet accessibility standards from the beginning. In the case of an alteration, the altered portion of the existing facility would have to be brought up to the same accessibility standards applicable to new facilities. For existing facilities not otherwise being altered, the PVO would have to ensure that the facility is able to be used by a passenger with a disability to access the PVO's vessel. This could be achieved through a variety of means. We note that there may be many situations in which a PVO shares accessibility responsibilities with another party. For example, a PVO may lease a portion of a port facility that is owned by a private or public entity. The PVO has responsibilities under this part; the other entity has responsibilities in its own right under Title II or III or the ADA or under section 504. In these cases, it would be up to the parties involved to allocate the responsibilities among themselves, so that they jointly ensure that accessibility requirements are met for the facility. We also recognize that there can be instances in which a vessel berths at a floating dock, rather than literally at a landside facility. We would propose to treat such a floating dock in the same way as a landside facility for accessibility purposes, but we seek comment on whether any different treatment would be appropriate. The Department seeks comment on whether it would be advisable to add specific provisions similar to §§ 37.41, 37.43, and 37.45 in the Department's existing ADA rule for the new construction and alteration of passenger vessel facilities, including provisions for alterations affecting areas containing a primary function that are subject to additional requirements for path of travel. § 39.63 What accommodations are required at terminals and other landside facilities for individuals with hearing or vision impairments? This section specifies the effective communications that would have to be provided at terminals and other landside facilities to ensure that persons with sensory impairments would be able to receive the information otherwise available to the public, concerning such subjects as ticketing, fares, and schedules. There would be a one-year phase-in period for this requirement, which would apply to existing as well as new facilities. Subpart E—Accessibility of Vessels This subpart would be reserved. It is a place-holder for the subsequent inclusion of passenger physical accessibility standards based on future Access Board guidelines. We note that, in connection with any rule incorporating the guidelines as DOT standards, DOT would designate an agency as the “administrative authority” to make certain determinations. We anticipate that the Department would designate the U.S. Coast Guard, with that agency's consent, as the administrative authority for many of these provisions, for foreign-flag as well as U.S. vessels. It is not necessary for this NPRM to propose this designation, since it logically would be part of a future NPRM proposing to adopt Access Board guidelines as DOT regulatory standards. There are, however, some facility accessibility issues that may not be covered by future Access Board guidelines. For example, we seek comment on whether a provision should be added for accessibility of televisions and telephones on vessels, similar to what DOT has proposed for air carriers pursuant to the Air Carrier Access Act (see 71 FR 9285 (February 23, 2006)). The Access Board's guidelines will not address televisions and telephones in passenger rooms since they are not fixed elements. It is our understanding that cruise ships typically provide televisions in passenger rooms and lounges. The Television Decoder Circuitry Act requires televisions with screens 13 inches or greater to contain built-in circuitry that receives and decodes closed captions. Cruise ships also typically provide telephones in passenger rooms. The Hearing Aid Compatibility Act and FCC rules require certain telephones to have volume controls and to be compatible with hearing aid technology. We seek information on whether cruise ships are currently providing televisions that are capable of receiving and decoding closed captions, and hearing aid compatible telephones with volume controls. The Department does not intend to impose requirements in this area in the final rule resulting from this NPRM. Rather, we are seeking comment on this subject in order to determine whether, in a future NPRM that would propose adoption of the Access Board's final passenger vessel guidelines, to propose adding requirements concerning telephones and televisions as a DOT modification to the guidelines. § 39.81 What assistance must PVOs provide to passengers with a disability in getting to and from a passenger vessel? This section does not deal with boarding a vessel, as such. Rather, it deals with how people get to the point of boarding a vessel, in terms of land transfers ( *e.g.* , a bus between the airport and the terminal) and in actually moving through the terminal and boarding process up to the point of getting onto the vessel. PVOs would be responsible for making sure that these services were accessible to people with disabilities. The Department seeks comment on the extent, if any, to which such a requirement should apply to services provided outside the U.S. ( *e.g.* , Grand Fenwick Cruise Lines itself provides, or contracts with a local bus company to provide, land transportation between the dock and points of interest in Barbados). § 39.83 What are PVOs' obligations for assisting passengers with a disability in getting on and off a passenger vessel? The optimal solution for boarding a vessel involves a passenger with a disability being able to board independently ( *e.g.* , via a level-entry ramp). The Department realizes that there will be many situations where this optimal solution does not exist. In these situations, the PVO is responsible for providing assistance that enables a passenger with a disability to get on or off the vessel. We note that a number of comments to the ANPRM represented that these services are already being provided in many instances, so we believe it is fair to suggest that this requirement would not create significant added burdens for PVOs. We also note that this provision pertains to normal boarding and disembarkation from a vessel: obviously, in the case of an “abandon ship” or other emergency situation, crew will use any means necessary to ensure that all passengers can safely evacuate. On some occasions, it may be the custom on cruise ships or other vessels with overnight accommodations to temporarily store luggage in passageways in preparation for disembarkation at the end of a voyage. This may have the effect of preventing passengers with disabilities from using otherwise accessible routes. The Department seeks comment on the extent of this problem and what requirements in a final rule, if any, should be devised to address it. The Department also seeks comment on whether a provision should be added that would require the use of accessible boarding systems, as described in § V412 of the Access Board's draft guidelines, for vessels with a certain passenger capacity at terminals that have a certain threshold level of annual embarkations, similar to the provision in DOT's Air Carrier Access rule. See 14 CFR 382.40(a). If so, what vessel passenger capacity and threshold level of annual embarkations should be used for requiring accessible boarding systems? Also, if a provision is added requiring accessible boarding systems at certain terminals, would it be advisable to require the PVO negotiate an agreement with the terminal operator to ensure the provision of accessible boarding systems, similar to the provision in DOT's Air Carrier Access Act and section 504 rules concerning boarding devices for commuter aircraft? See 14 CFR 382.40(b) and (c). Such an approach might also require amendment of the DOT 504 rule, 49 CFR Part 27. § 39.85 What services must PVOs provide to passengers with a disability on board a passenger vessel? § 39.87 What services are PVOs not required to provide to passengers with a disability on board a passenger vessel? These sections concern services that PVOs would, or need not, provide to passengers with a disability. The services in question include movement about the vessel, but only with respect to portions of the vessel that are not accessible to passengers with a disability acting independently. To the extent that a PVO makes accessibility improvements to a vessel, the PVO can probably reduce its obligation to provide this service. When food is provided to passengers, PVO personnel would help passengers with a disability to a limited degree, including opening packages and identifying food, or explaining choices. Assistance in actual eating or other personal functions ( *e.g.* , toileting or provision of medical equipment or supplies or assistive devices, beyond what is provided to all passengers) would not be required. Effective communication of on-board information would be required. § 39.89 What requirements apply to on-board safety briefings, information, and drills? This section specifies that safety-related information must be communicated effectively to passengers with disabilities. This can include the use of alternative formats and other auxiliary aids, where needed. Safety videos would have to be captioned or have an interpreter inset, in order to make the information available to persons with impaired hearing. Passengers with disabilities must be enabled to participate in evacuation and other safety drills, and information about evacuation and safety procedures would have to be kept in locations that passengers with disabilities can access and use. The Department seeks comment on whether any special accommodations would be needed to assist persons with cognitive disabilities. § 39.91 Must PVOs permit passengers with a disability to travel with service animals? Many persons with disabilities rely on service animals to travel and conduct daily functions. This section specifies that PVOs would be required to permit service animals to accompany a passenger with a disability on board a vessel. ICCL raised a number of service animal-related comments in its ANPRM response. We agree that foreign countries may limit entry of service animals; this should not affect the carriage of service animals on the vessel, however, since there is no requirement that the animal leave a cruise ship. Limitations on the ability of a service animal to leave the ship at a foreign port would be among the information that a cruise ship would provide to potential customers inquiring about an upcoming cruise. We also agree that PVOs would not be required to supply food for the animal. We seek comment on whether it is necessary to require PVOs to permit passengers with a disability to bring their own supplies of food for the service animal on board, without charge by the PVO. We also seek comment on whether PVOs should make refrigeration services available for service animal food. ICCL commented that service animals typically share the cabin of the passengers who use them. The Department does not see an objection to this practice, though we seek comment on whether service animal users have had any problems in this regard. We would view a limitation on the number of service animals that can be brought on a given voyage as tantamount to a number limit on passengers with a disability (i.e., as a number limit, which the proposed rule would prohibit). It is not self-evident that having a number of service animals on board a ship at a given time would be disruptive to ship operations, and vague concerns about adverse effects on the quality of the cruise experience for other passengers do not trump the nondiscrimination imperative of the ADA. The Department is not proposing, at this time, to adopt ACAA service animal guidance for other transportation contexts, though the general principles behind this guidance apply across the board to all transportation and public accommodations applications of the ADA. The Department anticipates that, following the publication of a final rule on passenger vessels, it would work with stakeholders to develop more detailed guidance on this subject for passenger vessels. One issue the Department would likely address in such guidance is the extent to which PVOs could inquire as to the status of an animal as a service animal ( *e.g.* , to prevent potential abuse from persons wanting to bring pets on board the vessel in ways inconsistent with the PVO's policy on pets). One issue that arises, especially in the context of longer voyages, concerns service animal relief areas. The Department seeks comment what requirements, if any, should be included in a final rule concerning the provision of such areas. Should a final rule specify the number and location of such areas? We are glad to see from the ICCL comment that cruise operators typically provide relief areas. ICCL, of course, represents the cruise industry, which frequently operates larger ships than other PVOs. The Department seeks comment on whether, with respect to any of the issues discussed in this section, there should be differing requirements for smaller vessels. § 39.93 What mobility aids and other assistive devices may passengers with a disability bring onto a passenger vessel? § 39.95 May PVOs limit their liability for the loss of or damage to mobility aids and other assistive devices? These sections say simply that passengers should be permitted to bring and use their own mobility aids and other assistive devices on board a vessel. Once the devices are there, if the PVO is responsible for loss or damage, the PVO must compensate the owner, at the level of the original purchase price of the device. This measure of the level of compensation is derived from the Department's ACAA rule. We also seek comment on alternative methods of measuring the appropriate level of compensation, such as the depreciated present value of the device or the current replacement cost for the device. § 39.101 What are the requirements for providing Complaints Resolution Officials? § 39.103 What actions do CROs take on complaints? The role of the Complaints Resolution Official
(CRO)was first developed in the Department's 1990 ACAA regulations, and it has proved very helpful in the airline service context. As applied in the passenger vessel context, the CRO would be the PVO's expert in disability matters, knowledgeable about both the Department's regulations and the PVO's procedures, and able to assist passengers with disabilities and other PVO personnel in resolving issues. We believe that the CRO model can potentially be adapted very well to passenger vessels, with the intent of solving problems at the PVO level before they become matters for complaints to the Department or for litigation. These proposed provisions are modeled closely on the ACAA CRO provisions, and the Department seeks comment on what changes, if any, should be made in adapting this model to passenger vessels. As in the airline context, the Department does not intend to mandate that CRO duties necessarily be full-time for a given employee. PVOs could, for example, train a number of different vessel and landside personnel to act as CROs, who might perform these functions as a collateral duty. PVOs are likely to find it necessary to ensure that not only CROs, but also other personnel who interact with passengers, are trained sufficiently to be knowledgeable about the requirements of these rules and proficient in performing tasks related to passengers with disabilities. If they are not, it is likely that mistakes will be made that would potentially lead to noncompliance. The Department seeks comment on what, if any, training requirements should be included in a final rule. One model that the Department could consider would resemble the training requirements in the ACAA rule. This model would involve training to proficiency concerning the requirements of this rule; the PVO's procedures with respect to the provision of transportation or use of a passenger vessel to passengers with a disability, including the proper and safe operation of any equipment used to accommodate passengers with a disability; the use of the equipment used by the PVO and appropriate assistance procedures that safeguard the safety and dignity of passengers. Training on the ACAA model would also address such matters as awareness and appropriate responses to passengers with a disability, including persons with physical, sensory, mental, and emotional disabilities, including how to distinguish among the differing abilities of individuals with a disability. Training on this model would cover contractor personnel as well as direct employees of PVOs. The Department seeks comment on whether such a requirement is advisable. We also seek comment on alternative training models that might be appropriate. The Department also seeks comment on what the costs of training are likely to be. With respect to training, the Department does not currently have data concerning the number of PVO personnel who would have to be trained or the costs per person of such training. We seek data from the industry or other sources on this matter. We point out that, in the regulatory evaluation for the Department's 2004 NPRM to expand ACAA coverage to foreign air carriers, the Department projected annual training costs of around $9.5 million, for an industry that probably has an affected work force of that may be of roughly comparable size. If there is such a training requirement, the Department seeks comment on what time frames or deadlines we should establish for completing the training. We also seek comment on what, if any, reporting or record retention requirements there should be concerning training. The Department does not, at this time, contemplate drafting a training curriculum or certifying the training of PVO personnel. § 39.105 How must PVOs respond to written complaints? § 39.107 Where may passengers file complaints? These provisions are also based on current ACAA procedures, and we again seek comment on how they may best be adapted to the passenger vessel context. We also seek comment on whether this rule should include a reporting requirement, analogous to that of the ACAA rule (see 14 CFR 382.70). The purpose of such a requirement would be to help the Department identify types of issues that may need additional attention or particular PVOs that may be having problems in a particular area in which the Department could focus compliance efforts. Should such a requirement be limited to PVOs operating vessels over a certain size ( *e.g.* , 50 passenger capacity)? Is a requirement similar to that of the ACAA a good idea in the vessel context, or is there a different or simpler approach we could take toward complaint reporting? The final rule would include detailed information on addresses, phone numbers, etc. where complaints could be filed at DOT or DOJ. Obviously, a passenger dissatisfied with the PVO's resolution of a complaint could file a complaint with DOT or DOJ. § 39.109 What enforcement action may be taken under this part? One important difference between the ACAA and the ADA is that, under the former, the Department has its own civil penalty enforcement authority and procedures. The Department does not have its own civil penalty authority under Titles II and III of the ADA, though the Department can conduct investigations and compliance reviews, collect data, find facts, come to conclusions, and refer matters to the Department of Justice for further action. DOJ can, of course, conduct enforcement proceedings on its own initiative. Some PVOs receive Federal financial assistance, such as ferry operators who receive Federal Transit Administration
(FTA)funding. Complaints concerning violations of this part by FTA-assisted ferry operators could be made to the FTA under the Department's ADA and 504 rules, and FTA could take enforcement action as provided in those rules. Regulatory Analyses and Notices The Department believes that this NPRM proposes a significant rule for Executive Order 12866 and DOT Regulatory Policies and Procedures purposes. While the NPRM does not impose significant costs, it addresses issues that are of considerable policy interest and would create requirements for entities that have not previously been subject to regulation. In a future rulemaking, the Department anticipates proposing, in conjunction with the Access Board, physical accessibility standards for vessels. This future rulemaking is expected to involve a more detailed regulatory evaluation with respect to the costs and benefits of its proposals, and it is also likely to be a significant rulemaking. This NPRM focuses on prohibiting unnecessary practices that have discriminatory effects, such as extra charges and denials of transportation. Observing such prohibitions will not have significant cost impacts on PVOs. According to ANPRM comments, many PVOs already provide boarding assistance and other services to passengers with disabilities, so it is reasonable to assume that the passenger assistance provisions of the NPRM would not have large incremental costs. We seek comment and data on these matters, however. As a general matter, we seek comment on whether any fuller regulatory evaluation or analysis concerning the cost of the proposed provisions or other matters should be developed in connection with the final rule. In the passenger vessel context as in other areas, the purpose of the ADA is to ensure nondiscrimination on the basis of disability and accessibility of travel on vessels for people with disabilities. Consequently, the most important benefits of this proposed rule are the largely non-quantifiable benefits of increased access and mobility for passengers with disabilities. These proposals would eliminate most policies of PVOs that would prevent or inhibit travel by persons with disabilities. The benefits that would accrue from removal of these barriers cannot be quantified, but could well include increased employment, business, recreational, and educational opportunities for travelers with disabilities, and quality of life enhancements associated with travel opportunities both within the U.S. and to foreign points. Many persons with mobility impairments would be able to use passenger vessel services for the first time, and take advantage of an expanded range of travel opportunities. Even persons with disabilities who did not immediately choose to use a passenger vessel would know that barriers to such travel had been removed, and there is a psychological benefit to knowing one can travel if one wishes (what economists sometimes refer to as the “option value” of a regulatory provision). Other beneficiaries of the proposed rule would include the travel companions, family, and friends of passengers with disabilities, since persons with disabilities would have greater and more varied travel opportunities. In addition, to the extent that changes in PVO practice make use of vessels easier for everyone, there would be indirect benefits for the general traveling public. Because making passenger vessel transportation and services more readily available to passengers with disabilities and others traveling with them is likely to increase overall usage of vessels to some degree, it is likely that there will be some economic benefits to PVOs from compliance with the proposed rule. The Department seeks data that would assist in quantifying these potential benefits. For the reasons stated above, the Department believes that compliance with the provisions proposed in this NPRM would have very low costs. That is, avoiding discriminatory policies and providing improved information to passengers with disabilities would not impose substantial costs on regulated parties generally. Therefore, the Department certifies that this NPRM, if adopted, would not have substantial economic effects on a significant number of small entities. Nevertheless, the Department seeks comment on small entity-related issues, including whether there should be provisions that mitigate any burdens on small entities resulting from the proposed requirements. This information would include data on numbers of companies and vessels (domestic and foreign-flag) that would be affected. In addition, the Department seeks comment on what standard should be used for analyzing small entity impacts with respect to passenger vessel transportation. Small Business Administration
(SBA)size standards in 13 CFR Part 121 establish a 500-employee standard (i.e., any entity with fewer employees would be regarded as a small business for SBA purposes). Is there any reason for using a different standard for purposes of this rulemaking (e.g., a PVO which does not operate any boats above a certain size)? While there are some state and local entities (i.e. operators of state or municipal ferry systems) that would be covered by this proposed rule, most regulated parties would be private sector entities. As noted above, we do not expect significant economic impacts on any regulated parties from the proposed rule. Consequently, we have concluded that there are not sufficient Federalism impacts to warrant the preparation of a Federalism assessment. As a civil rights rule, this proposal is not subject to review with respect to unfunded mandates. Issued this 5th day of January 2007, at Washington, DC. Mary E. Peters, Secretary of Transportation. List of Subjects for 49 CFR Part 39 Individuals with disabilities, Mass transportation, Passenger vessels. For the reasons set forth in the preamble, the Department of Transportation proposes to add a new 49 CFR Part 39, to read as follows: PART 39—TRANSPORTATION FOR INDIVIDUALS WITH DISABILITIES: PASSENGER VESSELS Subpart A—General Sec. 39.1 What is the purpose of this part? 39.3 What do the terms in this rule mean? 39.5 To whom do the provisions of this part apply? 39.7 What other authorities concerning nondiscrimination on the basis of disability apply to owners and operators of passenger vessels? 39.9 What may the owner or operator of a foreign-flag vessel do if it believes a provision of a foreign nation's law prohibits compliance with a provision of this part? 39.11 How may a PVO obtain approval to use an equivalent facilitation? 39.13 When must PVOs comply with the provisions of this part? Subpart B—Nondiscrimination and Access to Services 39.21 What is the general nondiscrimination requirement of this part? 39.23 What are the requirements concerning contractors to owners and operators of passenger vessels? 39.25 May PVOs limit the number of passengers with a disability on a passenger vessel? 39.27 May PVOs refuse to provide transportation or use of a vessel on the basis of disability? 39.29 May PVOs limit access to transportation or use of a vessel on the basis that a passenger has a communicable disease or other medical condition? 39.31 May PVOs require a passenger with a disability to provide a medical certificate? 39.33 May PVOs require a passenger with a disability to provide advance notice that he or she is traveling on or using a passenger vessel? 39.35 May PVOs require a passenger with a disability to provide advance notice in order to obtain certain specific services in connection with transportation on or use of a passenger vessel? 39.37 May PVOs require a passenger with a disability to travel with a personal or safety assistant? 39.39 May PVOs impose special charges on passengers with a disability for providing services and accommodations required by this rule? 39.41 May PVOs impose other restrictions on passengers with a disability that they do not impose on other passengers? 39.43 May PVOs require passengers with a disability to sign waivers or releases? Subpart C—Information for Passengers 39.51 What information must PVOs provide to passengers with a disability? 39.53 Must information and reservation services of PVOs be accessible to individuals with hearing or vision impairments? 39.55 Must PVOs make copies of this rule available to passengers? 39.57 What is the general requirement for PVOs' communications with passengers? Subpart D—Accessibility of Landside Facilities 39.61 What requirements must PVOs meet concerning the accessibility of terminals and other landside facilities? 39.63 What accommodations are required at terminals and other landside facilities for individuals with hearing or vision impairments? Subpart E—Accessibility of Vessels [Reserved] Subpart F—Assistance and Services to Passengers With Disabilities 39.81 What assistance must PVOs provide to passengers with a disability in getting to and from a passenger vessel? 39.83 What are PVOs' obligations for assisting passengers with a disability in getting on and off a passenger vessel? 39.85 What services must PVOs provide to passengers with a disability on board a passenger vessel? 39.87 What services are PVOs not required to provide to passengers with a disability on board a passenger vessel? 39.89 What requirements apply to on-board safety briefings, information, and drills? 39.91 Must PVOs permit passengers with a disability to travel with service animals? 39.93 What mobility aids and other assistive devices may passengers with a disability bring onto a passenger vessel? 39.95 May PVOs limit their liability for the loss of or damage to mobility aids and other assistive devices? Subpart G—Complaints and Enforcement Procedures 39.101 What are the requirements for providing Complaints Resolution Officials? 39.103 What actions do CROs take on complaints? 39.105 How must PVOs respond to written complaints? 39.107 Where may passengers file complaints? 39.109 What enforcement action may be taken under this part? Authority: 42 U.S.C. 12101 through 12213; 49 U.S.C. 322. Subpart A—General § 39.1 What is the purpose of this part? The purpose of this part is to carry out the Americans with Disabilities Act with respect to passenger vessels. This rule prohibits owners and operators of passenger vessels, including U.S. and foreign-flag vessels, from discriminating against passengers on the basis of disability; requires vessels and related facilities to be accessible; and requires owners and operators of vessels to take steps to accommodate passengers with a disability. § 39.3 What do the terms in this rule mean? In this regulation, the terms listed in this section have the following meanings: “Accessible” means, with respect to vessels and facilities, complying with the applicable accessibility requirements of this part. “Alteration” means a change to a passenger vessel or facility that affects or could affect the usability of the vessel, facility, or a portion thereof. Alterations include, but are not limited to, remodeling, renovation, rehabilitation, reconstruction, historic restoration, changes or rearrangement in structural parts or elements, and changes or rearrangement in the plan configuration of walls, bulkheads, and partitions. Normal maintenance, reroofing, painting or wallpapering, asbestos removal, or changes to propulsion, mechanical or electrical systems are not alterations unless they affect the usability of the passenger vessel or facility. “The Act” or “ADA” means the Americans with Disabilities Act of 1990 (Pub. L. 101-336, 104 Stat. 327, 42 U.S.C. 12101-12213 and 47 U.S.C. 225 and 611), as it may be amended from time to time. “Assistive device” means any piece of equipment that assists a passenger with a disability to cope with the effects of his or her disability. Such devices are intended to assist a passenger with a disability to hear, see, communicate, maneuver, or perform other functions of daily life, and may include medical devices and medications. “Auxiliary aids and services” includes:
(1)Qualified interpreters, notetakers, transcription services, written materials, telephone headset amplifiers, assistive listening devices, assistive listening systems, telephones compatible with hearing aids, closed caption decoders, closed and open captioning, text telephones (also known as telephone devices for the deaf, or TDDs), videotext displays, or other effective methods of making aurally delivered materials available to individuals with hearing impairments;
(2)Qualified readers, taped texts, audio recordings, Braille materials, large print materials, or other effective methods of making visually delivered materials available to individuals with visual impairments;
(3)Acquisition or modification of equipment or devices; or
(4)Other similar services or actions. “Coast Guard” means the United States Coast Guard, an agency of the Department of Homeland Security. “Commerce” means travel, trade, transportation, or communication among the several states, between any foreign country or any territory and possession and any state, or between points in the same state but through another state or foreign country. “Designated public transportation” means transportation provided by a public entity by passenger vessel that provides the general public with general or special service, including charter service, on a regular and continuing basis. “Department” or “DOT” means the United States Department of Transportation, including the Office of the Secretary of Transportation, the Federal Transit Administration, the Federal Highway Administration, and the Maritime Administration. “Direct threat” means a significant risk to the health or safety of others that cannot be eliminated by a modification of policies, practices, or procedures, or by the provision of auxiliary aids or services. “Disability” means, with respect to an individual, a physical or mental impairment that substantially limits one or more of the major life activities of such individual; a record of such an impairment; or being regarded as having such an impairment.
(1)(The phrase “physical or mental impairment” means—
(i)Any physiological disorder or condition, cosmetic disfigurement, or anatomical loss affecting one or more of the following body systems: neurological, musculoskeletal, special sense organs, respiratory including speech organs, cardiovascular, reproductive, digestive, genito-urinary, hemic and lymphatic, skin, and endocrine;
(ii)Any mental or psychological disorder, such as mental retardation, organic brain syndrome, emotional or mental illness, and specific learning disabilities.
(iii)The term “physical or mental impairment” includes, but is not limited to, such contagious or noncontagious diseases and conditions as orthopedic, visual, speech, and hearing impairments; cerebral palsy, epilepsy, muscular dystrophy, multiple sclerosis, cancer, heart disease, diabetes, mental retardation, emotional illness, specific learning disabilities, HIV disease, tuberculosis, drug addiction and alcoholism.
(iv)The phrase “physical or mental impairment” does not include homosexuality or bisexuality.
(2)The phrase “major life activities” means functions such as caring for one's self, performing manual tasks, walking, seeing, hearing, speaking, breathing, learning, and working;
(3)The phrase “has a record of such an impairment” means has a history of, or has been misclassified as having, a mental or physical impairment that substantially limits one or more major life activities.
(4)The phrase “is regarded as having such an impairment” means—
(i)Has a physical or mental impairment that does not substantially limit major life activities, but which is treated by a public or private entity as constituting such a limitation;
(ii)Has a physical or mental impairment that substantially limits a major life activity only as a result of the attitudes of others toward such an impairment; or
(iii)Has none of the impairments defined in paragraph
(1)of this definition but is treated by a public or private entity as having such an impairment.
(5)The term “disability” does not include—
(i)Transvestism, transsexualism, pedophilia, exhibitionism, voyeurism, gender identity disorders not resulting from physical impairments, or other sexual behavior disorders;
(ii)Compulsive gambling, kleptomania, or pyromania;
(iii)Psychoactive substance abuse disorders resulting from the current illegal use of drugs. “Existing vessel” means a passenger vessel in existence at the time of the effective date of Subpart E of this part. “Facility” means terminals and any of landside facilities related to the use of passenger vessels in the United States (including its territories, possessions, and commonwealths) that a vessel owner or operator owns, leases, or controls (e.g., terminals, boarding ramps, walks, parking lots, ticketing areas, baggage drop-off and retrieval sites) normally used by passengers or other members of the public. “Historic vessel” means a craft, ship, or boat of historic significance that is made available to the public to tour. Such vessels are usually permanently moored to a facility, but may take the public on excursions in some cases. “Individual with a disability” means a person who has a disability, but does not include an individual who is currently engaging in the illegal use of drugs, when a public or private entity acts on the basis of such use. “Operates” includes, with respect to passenger vessel service, the provision of transportation or other service by a public or private entity itself or by a person under a contractual or other arrangement or relationship with the entity. “Passenger for hire” means a passenger for whom consideration is contributed as a condition of carriage on the vessel, whether directly or indirectly flowing to the owner, charterer, operator, agent, or any other person having an interest in the vessel. “Passenger vessel” means any ship, boat, or other craft used as a conveyance on water, regardless of its means of propulsion, which accepts passengers for hire in connection with other revenue-generating activities. The term includes, but is not limited to, cruise ships, (whether U.S.- or foreign-flag); ferries; dinner, excursion, or sightseeing boats; boats chartered for fishing or other private recreational activities; and floating facilities used for gambling (whether tethered to a dock or mobile). The term does not include boats or other craft rented or leased to and operated solely by consumers. “Passenger vessel owner or operator (PVO)” means any public or private entity that owns or operates a passenger vessel. When the party that owns a passenger vessel is a different party from the party that operates the vessel, both are responsible for complying with the requirements of this part. The term includes entities that are primarily engaged in the business of transporting people (e.g., a cruise ship or excursion vessel) and entities that are not primarily engaged in transporting people (e.g., an amusement park operator which operates a passenger vessel to transport visitors from a parking area to the main part of the park or a hotel located on an island that operates a passenger vessel to shuttle guests from the mainland to the island). “Private entity” means any entity other than a public entity. “Public entity” means:
(1)Any state or local government;
(2)Any department, agency, special purpose district, or other instrumentality of one or more state or local governments (including an entity established to provide public ferry service). “Purchase or lease,” with respect to passenger vessels, means the time at which an entity is legally obligated to obtain a vessel, such as the time of contract execution. “Qualified individual with a disability” means an individual with a disability—
(1)Who, as a passenger (referred to as a “passenger with a disability”),
(i)With respect to obtaining a ticket for transportation on passenger vessel offers, or makes a good faith attempt to offer, to purchase or otherwise validly to obtain such a ticket;
(ii)With respect to obtaining transportation on or use of a passenger vessel, or other services or accommodations required by this part,
(A)Buys or otherwise validly obtains, or makes a good faith effort to obtain, a ticket for transportation on a passenger vessel and presents himself or herself at the vessel for the purpose of traveling on the voyage to which the ticket pertains; or
(B)With respect to use of a passenger vessel for which members of the public are not required to obtain tickets, presents himself or herself at the vessel for the purpose of using the vessel for the purpose for which it is made available to the public; and
(C)Meets reasonable, nondiscriminatory requirements applicable to all passengers; or
(2)Who, with respect to accompanying or meeting a traveler, using ground transportation, using facilities, or obtaining information about schedules, fares, reservations, or policies, takes those actions necessary to use facilities or services offered by the PVO to the general public, with reasonable accommodations, as needed, provided by the PVO. “Secretary” means the Secretary of Transportation or his/her designee. “Section 504” means section 504 of the Rehabilitation Act of 1973 (Pub. L. 93-112, 87 Stat. 394, 29 U.S.C. 794), as amended. “Service animal” means any guide dog, signal dog, or other animal individually trained to work or perform tasks for an individual with a disability, including, but not limited to, guiding individuals with impaired vision, alerting individuals with impaired hearing to intruders or sounds, alerting persons with seizure disorders to the onset of a seizure, providing minimal protection or rescue work, pulling a wheelchair, or fetching dropped items. “Solicitation” means the closing date for the submission of bids or offers in a procurement. “Specified public transportation” means transportation by passenger vessel provided by a private entity to the general public, with general or special service (including charter service) on a regular and continuing basis. “Terminal” means, with respect to passenger vessel transportation, the portion of a property located appurtenant to a dock, entry ramp, or other means of boarding a passenger vessel, including areas of interface with land transportation, passenger shelters, designated waiting areas, restrooms, concession areas, ticketing areas, and baggage drop-off and retrieval sites,to the extent that the PVO owns or leases the facility or exercises control over the selection, design, construction, or alteration of the property. “United States” or “U.S.” means the United States of America, including its territories, commonwealths, and possessions. “Wheelchair” means a mobility aid belonging to any class of wheeled devices, usable indoors, designed or adapted for and used by individuals with disabilities, whether operated manually or powered. A “common wheelchair” is such a device which does not exceed 30 inches in width and 48 inches in length measured two inches above the ground, and does not weigh more than 600 pounds when occupied. “You” means the owner or operator of a passenger vessel, unless the context requires a different meaning. § 39.5 To whom do the provisions of this part apply?
(a)Except as provided in paragraph
(b)or
(c)of this section, this part applies to you if you are the owner or operator of any passenger vessel, and you are:
(1)A public entity that provides designated public transportation;
(2)A private entity primarily engaged in the business of transporting people whose operations affect commerce that provides specified public transportation; or
(3)A private entity that owns, operates, or leases a place of public accommodation, and you are not primarily engaged in the business of transporting people.
(b)If you are the PVO of a foreign-flag passenger vessel, this part applies to you only if your vessel picks up passengers at a port in the United States, its territories, possessions, or commonwealths.
(c)[Reserved] § 39.7 What other authorities concerning nondiscrimination on the basis of disability apply to owners and operators of passenger vessels?
(a)If you receive Federal financial assistance from the Department of Transportation, compliance with applicable requirements of this part is a condition of compliance with section 504 of the Rehabilitation Act of 1973 and of receiving financial assistance.
(b)You are also subject to ADA regulations of the Department of Justice (28 CFR Parts 35 or 36, as applicable). The provisions of this part shall be interpreted in a manner that will make them consistent with applicable Department of Justice regulations. In any case of apparent inconsistency, the provisions of this part shall prevail. § 39.9 What may the owner or operator of a foreign-flag vessel do if it believes a provision of a foreign nation's law prohibits compliance with a provision of this part?
(a)If you are the PVO of a foreign-flag vessel, and you believe that a binding legal requirement of a foreign nation precludes you from complying with a provision of this part, you may request a waiver of the provision of this part.
(b)You must send such a waiver request to the Department.
(c)Your waiver request must include the following elements:
(1)A copy, in the English language, of the foreign law involved;
(2)A description of how the binding legal requirement of a foreign nation applies and how it precludes compliance with a provision of this part;
(3)A description of the alternative means you will use, if the waiver is granted, to effectively achieve the objective of the provision of this part subject to the waiver or, if applicable, a justification of why it would be impossible to achieve this objective in any way.
(d)If you submit such a waiver request in the 90-day period between the publication of this rule in the **Federal Register** and the effective date of this part, you may continue to apply the foreign legal requirement pending the Department's response to your waiver request.
(e)The Department may grant the waiver request if it determines that the binding legal requirement of a foreign nation applies, that it does preclude compliance with a provision of this part, and that the PVO has provided an effective alternative means of achieving the objective of the provision of this part subject to the waiver or clear and convincing evidence that it would be impossible to achieve this objective in any way. § 39.11 How may a PVO obtain approval to use an equivalent facilitation?
(a)Nothing in this part prevents the use of designs, products, or technologies as alternatives to those prescribed in this part, or alternative ways of providing accommodations and services to passengers with disabilities, provided they result in substantially equivalent or greater accessibility and usability.
(b)If, as a PVO or the manufacturer of a product or accessibility feature to be used in a passenger vessel, you wish to provide an equivalent facilitation in lieu of complying with a provision of this part, you may request approval to do so from the Department.
(c)You must use the following process to request approval of an equivalent facilitation:
(1)You must provide the following information with your request:
(i)Entity name, address, contact person, and telephone;
(ii)Specific provision(s) of this part or 49 CFR Part 38 concerning which the entity is seeking a determination of equivalent facilitation.
(iii)Alternative method of compliance, with demonstration of how the alternative meets or exceeds the level of accessibility or usability of the vessel provided this part.
(2)Before you submit your request for equivalent facilitation, you must provide opportunities for public participation:
(i)You must consult in person, in writing, or by other appropriate means, with individuals with disabilities and groups representing them, as well as conduct outreach to passengers, particularly those with disabilities. This consultation must take place at all stages of the development of the request for equivalent facilitation. All documents and other information concerning the request shall be available, upon request, to the Department and members of the public.
(ii)You must make your proposed request available for public review and comment before the request is made final or transmitted to DOT. In making the request available for public review, you must ensure that it is available, upon request, in accessible formats.
(3)A determination whether to approve or disapprove your request, in whole or in part, will be made by the Department on a case-by-case basis. Determinations are made by the General Counsel, with the concurrence of the Assistant Secretary for Transportation Policy.
(i)An approval may be conditioned on specified actions that you agree to take.
(ii)The Department normally considers approving an equivalent facilitation only with respect to the specific situation concerning which the request is made. However, the Department may approve a request for equivalent facilitation with respect to a product or accessibility feature that the Department determines can provide an equivalent facilitation in a class of situations. (4)(i) You must not cite an approval of a request for equivalent facilitation as indicating that a product or method constitutes equivalent facilitation in situations, or classes of situations, other than those to which the determination specifically pertains.
(ii)You must not claim that a determination of equivalent facilitation indicates approval or endorsement of any product or method by the Federal government or the Department of Transportation. § 39.13 When must PVOs comply with the provisions of this part? You are required to comply with the requirements of this part beginning [insert effective date of the final rule], except as otherwise provided in individual sections of this part. Subpart B—Nondiscrimination and Access to Services § 39.21 What is the general nondiscrimination requirement of this part?
(a)As a PVO, you must not do any of the following things, either directly or through a contractual, licensing, or other arrangement:
(1)You must not discriminate against any qualified individual with a disability, by reason of such disability, with respect to the individual's use of the vessel;
(2)You must not require a qualified individual with a disability to accept special services that the individual does not request;
(3)You must not exclude a qualified individual with a disability from or deny the person the benefit of any vessel transportation or related services that are available to other persons. This is true even if there are separate or different services available for individuals with a disability, except when specifically permitted by another section of this part; and
(4)You must not take any action against an individual ( *e.g.* , refusing to provide transportation) because the individual asserts, on his or her own behalf or through or on behalf of others, rights protected by this part or the ADA.
(b)You must make reasonable modifications in policies, practices, or procedures when the modifications are necessary to avoid discrimination on the basis of disability or to provide program accessibility to your services, unless you can demonstrate that doing so would fundamentally alter the nature of the service, program, or activity, or would result in undue administrative or financial burdens. § 39.23 What are the requirements concerning contractors to owners and operators of passenger vessels?
(a)If, as a PVO, you enter into a contractual or other arrangement or relationship with any other party to provide services to or affecting passengers, you must ensure that the other party meets the requirements of this part that would apply to you if you provided the service yourself.
(b)As a PVO, you must include an assurance of compliance with this part in your contracts with any contractors who provide to the public services that are subject to the requirements of this part. Noncompliance with this assurance is a material breach of the contract on the contractor's part.
(1)This assurance must commit the contractor to compliance with all applicable provisions of this part in activities performed on behalf of the PVO.
(2)The assurance must also commit the contractor to implementing directives issued by your Complaints Resolution Officials
(CROs)under § 39.103.
(c)As a PVO, you must also include such an assurance of compliance in your contracts or agreements of appointment with U.S. travel agents. You are not required to include such an assurance in contracts with foreign travel agents.
(d)You remain responsible for your contractors' compliance with this part and with the assurances in your contracts with them.
(e)It is not a defense to an enforcement action under this part that your noncompliance resulted from action or inaction by a contractor. § 39.25 May PVOs limit the number of passengers with a disability on a passenger vessel? As a PVO, you must not limit the number of passengers with a disability on your vessel. § 39.27 May PVOs refuse to provide transportation or use of a vessel on the basis of disability?
(a)As a PVO, you must not refuse to provide transportation or use of a vessel to a passenger with a disability on the basis of his or her disability, except as specifically permitted by this part.
(b)You must not refuse to provide transportation or use of a vessel to a passenger with a disability because the person's disability results in appearance or involuntary behavior that may offend, annoy, or inconvenience crewmembers or other passengers.
(c)You may refuse to provide transportation or use of a vessel to any passenger on the basis of safety only as provided in this paragraph:
(1)You can determine that there is a disability-related safety basis for refusing to provide transportation or use of a vessel to a passenger with a disability if you are able to demonstrate that the passenger poses a direct threat (see definition in § 39.3). In determining whether an individual poses a direct threat, you must make an individualized assessment, based on reasonable judgment that relies on current medical knowledge or on the best available objective evidence, to ascertain:
(i)the nature, duration, and severity of the risk;
(ii)the probability that the potential harm to the health and safety of others will actually occur; and
(iii)whether reasonable modifications of policies, practices, or procedures will mitigate the risk.
(2)If you determine that the passenger does pose a direct threat, you must select the least restrictive response from the point of view of the passenger, consistent with protecting the health and safety of others. For example, you must not refuse transportation or use of the vessel to the passenger if you can protect the health and safety of others by means short of a refusal (e.g., by implementing measures recommended by a physician in connection with a medical certificate under § 39.31 to prevent the transmission of a disease).
(d)If you refuse to provide transportation or use of a vessel to a passenger on a basis relating to the individual's disability, you must provide to the person a written statement of the reason for the refusal. This statement must include the specific basis for your opinion that the refusal meets the standards of paragraph
(c)of this section or is otherwise specifically permitted by this part. You must provide this written statement to the person within 10 calendar days of the refusal of transportation or use of the vessel. § 39.29 May PVOs limit access to transportation or use of a vessel on the basis that a passenger has a communicable disease or other medical condition?
(a)You must not do any of the following things on the basis that a passenger has a communicable disease or infection, unless you determine that the passenger's condition poses a direct threat:
(1)Refuse to provide transportation or use of a vessel to the passenger;
(2)Delay the passenger's transportation or use of the vessel (e.g., require the passenger to take a later trip);
(3)Impose on the passenger any condition, restriction, or requirement not imposed on other passengers; or
(4)Require the passenger to provide a medical certificate.
(b)In assessing whether the passenger's condition poses a direct threat, you must consider the following factors:
(1)Whether U.S. or international public health authorities (e.g., the Centers for Disease Control, Public Health Service, World Health Organization) have determined that persons with a particular condition should not be permitted to travel;
(2)Whether an individual has a condition that is both readily transmissible by casual contact in the context of traveling on or using a passenger vessel and has serious health consequences;
(3)Whether applying the provisions of § 39.27 (c)(1) through
(2)would otherwise lead to the conclusion that the person poses a direct threat to the health or safety of others.
(c)If your action under this section results in the postponement of a passenger's transportation or use of the vessel, you must permit the passenger to travel or use the vessel at a later time (up to one year from the date of the postponed trip or use of the vessel) at the cost that would have applied to the passenger's originally scheduled trip or use of the vessel without penalty or, at the passenger's discretion, provide a refund for any unused transportation or use of the vessel.
(d)If you take any action under this section that restricts a passenger's transportation or use of the vessel, you must, on the passenger's request, provide a written explanation within 10 days of the request. § 39.31 May PVOs require a passenger with a disability to provide a medical certificate?
(a)Except as provided in this section, you must not require a passenger with a disability to have a medical certificate as a condition for being provided transportation. (b)(1) You may require a medical certificate for a passenger with a disability—
(i)Who needs medical oxygen during his or her transportation or use of the vessel; or
(ii)Whose medical condition is such that there is reasonable doubt that the individual can complete the transportation or use of the vessel safely, without requiring extraordinary medical assistance.
(2)For purposes of this paragraph, a medical certificate is a written statement from the passenger's physician saying that the passenger is capable of completing the transportation or use of the vessel safely, without requiring extraordinary medical assistance. (c)(1) You may also require a medical certificate for a passenger if he or she has a communicable disease or condition that poses a direct threat to the health or safety of others.
(2)For purposes of this paragraph, a medical certificate is a written statement from the passenger's physician saying that the disease or infection would not, under the present conditions in the particular passenger's case, be communicable to other persons during the normal course of the passenger's transportation or use of the vessel. The medical certificate must state any conditions or precautions that would have to be observed to prevent the transmission of the disease or infection to other persons in the normal course of the passenger's transportation on or use of the vessel. It must be dated within 10 days of the date of the trip or use of the vessel for which it is presented. § 39.33 May PVOs require a passenger with a disability to provide advance notice that he or she is traveling on or using a passenger vessel? As a PVO, you must not require a passenger with a disability to provide advance notice of the fact that he or she is traveling on or using a passenger vessel. § 39.35 May PVOs require a passenger with a disability to provide advance notice in order to obtain certain specific services in connection with transportation on or use of a passenger vessel?
(a)Except as provided in paragraph
(b)of this section, as a PVO you must not require a passenger with a disability to provide advance notice in order to obtain services or accommodations required by this part.
(1)If 10 or more passengers with a disability seek to travel as a group, you may require 72 hours advance notice for the group's travel.
(2)If a passenger needs an accessible overnight cabin, you may require 72 hours advance notice for the accommodation. In order to ensure that such accommodations remain available for passengers with a disability, you must inform other passengers who reserve accessible cabins that, if a person with a disability requests the accommodation by 72 hours before the vessel's scheduled departure, you will move the other person to a different cabin.
(c)If the passenger with a disability provides the advance notice you require, consistent with this section, for a service, then you must provide the requested service or accommodation.
(d)Your reservation and other administrative systems must ensure that when passengers provide the advance notice that you require, consistent with this section, for services and accommodations, the notice is communicated, clearly and on time, to the people responsible for providing the requested service or accommodation.
(e)If a passenger does not meet advance notice or check-in requirements you establish consistent with this section, you must still provide the service or accommodation if you can do so by making reasonable efforts, without delaying the trip. § 39.37 May PVOs require a passenger with a disability to travel with a personal or safety assistant?
(a)Except as provided in paragraph
(b)of this section, you must not require that a passenger with a disability travel with another person as a condition of being provided transportation on or use of a passenger vessel.
(b)You may require a passenger with a disability in one of the following categories to travel with a safety assistant as a condition of being provided transportation or use of a passenger vessel, if you determine that a safety assistant is essential for safety:
(1)A passenger who, because of a mental disability, is unable to comprehend or respond appropriately to safety instructions from vessel personnel.
(2)A passenger with a mobility impairment so severe that the person is unable to assist in his or her own evacuation from the vessel in an emergency;
(3)A passenger who has both severe hearing and severe vision impairments, if the person cannot establish some means of communication with vessel personnel for purposes of safety information and instructions.
(c)You may require a passenger with a disability to have a personal assistant if the passenger is unable to perform personal tasks (e.g., eating, dressing, toileting) without such an assistant, and the duration of the transportation or use of the vessel is long enough that the passenger must perform one or more of these tasks while on the vessel.
(d)If you determine that a person meeting the criteria of paragraph
(b)or
(c)of this section must travel with a safety or personal assistant, contrary to the individual's self-assessment that he or she is capable of traveling independently, you must not charge for the transportation of the safety assistant. You may also designate a member of your staff or a passenger volunteer to perform the personal or safety assistant role in such a case, rather than carrying at no charge a person designated by the passenger. In a case in which a passenger voluntarily chooses to travel with a personal assistant or a safety assistant that you do not require, you may charge for the transportation of that person. § 39.39 May PVOs impose special charges on passengers with a disability for providing services and accommodations required by this rule?
(a)As a PVO, you must not charge higher fares, surcharges, or other fees to passengers with a disability that are not imposed on other passengers for transportation or use of the vessel.
(b)If the accommodations on a vessel that are accessible to passengers with a disability are in a type or class of service or part of a vessel that are more expensive than the type or class of service or past of[A3] a vessel that the passenger requests, you must provide the accessible accommodation at the price of the type or class of service or facility that the passenger requests.
(c)You must not impose special or extra charges for providing facilities, equipment, accommodations, or services that this rule requires to be provided to passengers with a disability. § 39.41 May PVOs impose other restrictions on passengers with a disability that they do not impose on other passengers?
(a)As a PVO, you must not subject passengers with a disability to restrictions that do not apply to other passengers, except as otherwise explicitly permitted in this part.
(b)Restrictions you must not impose on passengers with a disability include, but are not limited to, the following:
(1)Restricting passengers' movement within the vessel or a terminal;
(2)Requiring passengers to remain in a holding area or other location in order to receive transportation, services, or accommodations;
(3)Requiring passengers to wear badges or other special identification; or
(4)Requiring ambulatory passengers, including but not limited to blind or visually impaired passengers, to use a wheelchair in order to receive assistance required by this part or otherwise offered to the passenger. § 39.43 May PVOs require passengers with a disability to sign waivers or releases?
(a)As a PVO, you must not require passengers with a disability to sign any release or waiver of liability in order to receive transportation or use of a vessel or to receive services or accommodations for a disability.
(b)You must not require passengers with a disability to sign waivers of liability for damage to or loss of wheelchairs or other assistive devices. Subpart C—Information for Passengers § 39.51 What information must PVOs provide to passengers with a disability? As a PVO, you must provide the following information to passengers who self-identify as having a disability or who request disability-related information, or persons making inquiries on the behalf of such persons. The information you provide must, to the maximum extent feasible, be specific to the vessel a person is seeking to travel on or use.
(a)The availability of accessible facilities on the vessel; including, but not limited to, means of boarding the vessel, lavatories, staterooms, decks, dining, and recreational facilities;
(b)Any limitations on the ability of the vessel to accommodate passengers with a disability;
(c)Any limitations on the accessibility of boarding and disembarking at ports at which the vessel will call and services or tours ancillary to the transportation provided by the vessel concerning which the PVO makes arrangements available to passengers. § 39.53 Must information and reservation services of PVOs be accessible to individuals with hearing or vision impairments? This section applies to information and reservation services made available to persons in the United States.
(a)If, as a PVO, you provide telephone reservation or information service to the public, you must make this service available to individuals who are deaf or hard-of-hearing through use of a text telephone (TTY).
(1)You must make TTY service available during the same hours as telephone service for the general public.
(2)Your response time to TTY calls must be equivalent to your response time for your telephone service to the general public.
(3)You must meet this requirement by [date one year from the effective date of the final rule].
(b)If, as a PVO, you provide written (i.e., hard copy) information to the public, you must ensure that this information is able to be communicated effectively, on request, to persons with vision impairments. You must provide this information in the same languages(s) in which it is available to the general public. § 39.55 Must PVOs make copies of this rule available to passengers? As a PVO, you must keep a current copy of this part on each vessel and each U.S. port or terminal you serve and make it available to passengers on request. § 39.57 What is the general requirement for PVOs' communications with passengers? PVOs must ensure the effective communication to passengers with disabilities of all information provided to passengers, through the use of auxiliary aids where needed. Subpart D—Accessibility of Landside Facilities § 39.61 What requirements must PVOs meet concerning the accessibility of terminals and other landside facilities? As a PVO, you must comply with the following requirements with respect to all terminal and other landside facilities you own, lease, or control in the United States (including its territories, possessions, and commonwealths):
(a)With respect to new facilities, you must do the following:
(1)You must ensure that terminal facilities are readily accessible to and usable by individuals with disabilities, including individuals who use wheelchairs. You are deemed to comply with this obligation if the facilities meet requirements of 49 CFR Part 37, § 37.9, and the standards referenced in that section.
(2)You must ensure that there is an accessible path between the terminal or other passenger waiting area and the boarding ramp or device used for the vessel. An accessible route is one meeting the requirements of the standards referenced in 49 CFR Part 37, § 37.9.
(b)When a facility is altered, the altered portion must meet the same standards that would apply to a new facility.
(c)With respect to an existing facility, you must ensure that passengers with a disability can use the facility to gain access to your vessel. You may meet this obligation through any combination of facility accessibility, equipment, the assistance of personnel, or other appropriate means consistent with the safety and dignity of passengers with a disability. With respect to making structural modifications in existing facilities, you have the same obligations as any other public or private entity under the applicable provisions of DOT ADA regulations.
(d)Where you share responsibility for ensuring accessibility of a facility with another entity, you and the other entity are jointly and severally responsible for meeting applicable accessibility requirements. § 39.63 What accommodations are required at terminals and other landside facilities for individuals with hearing or vision impairments?
(a)As a PVO, the information you provide to the general public at terminals and other landside facilities must be effectively communicated to individuals with impaired vision and deaf and hard-of-hearing individuals. To the extent that this information is not available to these individuals through signage and/or verbal public address announcements, your personnel must promptly provide the information to such individuals on their request, in languages in which the information is provided to the general public.
(b)The types of information you must make available include, but are not limited to, information concerning ticketing, fares, schedules and delays, and the checking and claiming of luggage.
(c)You must meet the requirements of this section by [date one year from effective date of the final rule]. Subpart E—Accessibility of Vessels [Reserved] Subpart F—Assistance and Services to Passengers With Disabilities § 39.81 What assistance must PVOs provide to passengers with a disability in getting to and from a passenger vessel?
(a)As a PVO, if you provide, contract for, or otherwise arrange for transportation to and from a passenger vessel (e.g., a bus transfer from an airport to a vessel terminal), you must ensure that the transfer service is accessible to and usable by individuals with disabilities, as required by this part.
(b)You must also provide assistance requested by or on behalf of a passenger with a disability in moving between the terminal entrance (or a vehicle drop-off point adjacent to the entrance) and the place where people get on or off the passenger vessel. This requirement includes assistance in accessing key functional areas of the terminal, such as ticket counters and baggage checking/claim. It also includes a brief stop upon request at an accessible restroom or nearby takeout food vendor. § 39.83 What are PVOs' obligations for assisting passengers with a disability in getting on and off a passenger vessel?
(a)If a passenger with a disability can readily get on or off a passenger vessel without assistance, you are not required to provide such assistance to the passenger. You must not require such a passenger with a disability to accept assistance from you in getting on or off the vessel.
(b)With respect to a passenger with a disability who is not able to get on or off a passenger vessel without assistance, you must promptly provide assistance that ensures that the passenger can get on or off the vessel.
(c)When you have to provide assistance to a passenger with a disability in getting on or off a passenger vessel, you may use any available means to which the passenger consents (e.g., lifts, ramps, boarding chairs, assistance by tour personnel). However, you must never use hand-carrying (i.e., directly picking up the passenger's body in the arms of one or more personnel) to effect a level change the passenger needs to get on or off the vessel, even if the passenger consents. § 39.85 What services must PVOs provide to passengers with a disability on board a passenger vessel? As a PVO, you must provide services on board the vessel as requested by or on behalf of passengers with a disability, or when offered by PVO personnel and accepted by passengers with a disability, as follows:
(a)Assistance in moving about the vessel, with respect to any spaces that are not readily accessible and usable to the passenger.
(b)If food is provided to passengers on the vessel, assistance in preparation for eating, such as opening packages and identifying food;
(c)Effective communication with passengers who have vision impairments or who are deaf or hard-of-hearing, so that these passengers have timely access to information the PVO provides to other passengers (e.g., weather, on-board services, delays). § 39.87 What services are PVOs not required to provide to passengers with a disability on board a passenger vessel? As a PVO, you are not required to provide extensive special assistance to passengers with a disability. For purposes of this section, extensive special assistance includes the following activities:
(a)Assistance in actual eating;
(b)Assistance within a restroom or assistance elsewhere on the vessel with elimination functions; and
(c)Provision of medical equipment or services, or assistive devices, except to the extent provided to all passengers. § 39.89 What requirements apply to on-board safety briefings, information, and drills? As a PVO, you must comply with the following requirements with respect to safety briefings, information, or drills provided to passengers:
(a)You must provide the briefings or other safety-related information through means that effectively communicate their content to persons with vision or hearing impairments. This includes providing written materials in alternative formats that persons with vision impairments can use.
(b)You must not require any passenger with a disability to demonstrate that he or she has listened to, read, or understood the information presented, except to the extent that you impose such a requirement on all passengers. You must not take any action adverse to a qualified individual with a disability on the basis that the person has not “accepted” the briefing.
(c)As a PVO, if you present on-board safety briefings to passengers on video screens, you must ensure that the safety-video presentation is accessible to passengers with impaired hearing (e.g., through use of open captioning or placement of a sign language interpreter in the video).
(1)You may use an equivalent non-video alternative to this requirement only if neither open captioning nor a sign language interpreter inset can be placed in the video presentation without so interfering with it as to render it ineffective or it would not be large enough to be readable.
(2)You may implement the requirements of this section by substituting captioned or interpreted video materials for uncaptioned/uninterpreted video materials as the uncaptioned/uninterpreted materials are replaced in the normal course of the carrier's operations.
(d)You must provide whatever assistance is necessary to enable passengers with disabilities to participate fully in safety or emergency evacuation drills provided to all passengers.
(e)You must maintain evacuation programs, information, and equipment in locations that passengers can readily access and use. § 39.91 Must PVOs permit passengers with a disability to travel with service animals?
(a)As a PVO, you must permit service animals to accompany passengers with a disability.
(b)You must permit the service animal to accompany the passenger in all locations that passengers can use on a vessel.
(c)You must accept the following as evidence that an animal is a service animal: identification cards, other written documentation, presence of harnesses, tags, and/or the credible verbal assurances of a passenger with a disability using the animal.
(d)If you decide not to accept an animal as a service animal, you must explain the reason for your decision to the passenger and document it in writing. A copy of the explanation must be provided to the passenger within 10 calendar days of the incident. § 39.93 What mobility aids and other assistive devices may passengers with a disability bring onto a passenger vessel?
(a)As a PVO, you must permit passengers with a disability to bring the following kinds of items onto a passenger vessel, consistent with Coast Guard requirements concerning security, safety, and hazardous materials:
(1)Wheelchairs and other mobility devices, including, but not limited to, manual wheelchairs and battery-powered wheelchairs;
(2)Other mobility aids, such as canes (including those used by persons with impaired vision), crutches, and walkers;
(3)Other assistive devices (e.g., vision-enhancing devices, personal ventilators, portable oxygen concentrators, and respirators that use non-spillable batteries);
(4)Personal oxygen supplies.
(b)You must permit passengers with a disability to use their mobility aids and assistive devices on board the vessel in all locations passengers access.
(c)You are not required to permit passengers with a disability to bring these items into lifeboats or other survival craft, in the context of an emergency evacuation of the vessel. § 39.95 May PVOs limit their liability for loss of or damage to mobility aids or other assistive devices? Consistent with any applicable requirements of international law, you must not apply any liability limits with respect to loss of or damage to wheelchairs or other assistive devices. The criterion for calculating the compensation for a lost, damaged, or destroyed wheelchair or other assistive device shall be the original purchase price of the device. Subpart G—Complaints and Enforcement Procedures § 39.101 What are the requirements for providing Complaints Resolution Officials?
(a)As a PVO, you must designate one or more Complaints Resolution Officials (CROs).
(b)You must make a CRO available on each vessel and each terminal you serve. You must make CRO service available in the language(s) in which you make your other services available to the general public.
(c)You may make the CRO available in person or via telephone, at no cost to the passenger. If a telephone link to the CRO is used, TTY service must be available so that persons with hearing impairments may readily communicate with the CRO.
(d)You must make passengers with a disability aware of the availability of a CRO and how to contact the CRO in the following circumstances:
(1)In any situation in which any person complains or raises a concern with your personnel about discrimination, accommodations, or services with respect to passengers with a disability, and your personnel do not immediately resolve the issue to the customer's satisfaction or provide a requested accommodation, your personnel must immediately inform the passenger of the right to contact a CRO and the location and/or phone number of the CRO available on the vessel or at the terminal. Your personnel must provide this information to the passenger in a format he or she can use.
(2)Your reservation agents, contractors, and web sites must provide information equivalent to that required by paragraph (d)(1) of this section to passengers with a disability using those services.
(e)Each CRO must be thoroughly familiar with the requirements of this part and the carrier's procedures with respect to passengers with a disability. The CRO is intended to be the PVO's “expert” in compliance with the requirements of this part.
(f)You must ensure that each of your CROs has the authority to make dispositive resolution of complaints on behalf of the PVO. This means that the CRO must have the power to overrule the decision of any other personnel, except that the CRO is not required to be given authority to countermand a decision of the master of a vessel with respect to safety matters. § 39.103 What actions do CROs take on complaints? When a complaint is made directly to a CRO (e.g., orally, by phone, TTY) the CRO must promptly take dispositive action as follows:
(a)If the complaint is made to a CRO before the action or proposed action of PVO personnel has resulted in a violation of a provision of this part, the CRO must take, or direct other PVO personnel to take, whatever action is necessary to ensure compliance with this part.
(b)If an alleged violation of a provision of this part has already occurred, and the CRO agrees that a violation has occurred, the CRO must provide to the complainant a written statement setting forth a summary of the facts and what steps, if any, the PVO proposes to take in response to the violation.
(c)If the CRO determines that the PVO's action does not violate a provision of this part, the CRO must provide to the complainant a written statement including a summary of the facts and the reasons, under this part, for the determination.
(d)The statements required to be provided under this section must inform the complainant of his or her right complain to the Department of Transportation and/or Department of Justice. The CRO must provide the statement in person to the complainant in person if possible; otherwise, it must be transmitted to the complainant within 10 calendar days of the complaint. § 39.105 How must PVOs respond to written complaints?
(a)As a PVO, you must respond to written complaints received by any means (e.g., letter, fax, e-mail, electronic instant message) concerning matters covered by this part.
(b)A passenger making a written complaint, must state whether he or she had contacted a CRO in the matter, provide the name of the CRO and the date of the contact, if available, and enclose any written response received from the CRO.
(c)As a PVO, you are not required to respond to a complaint postmarked or transmitted more than 45 days after the date of the incident, except for complaints referred to you by the Department of Transportation.
(d)As a PVO, you must make a dispositive written response to a written disability complaint within 30 days of its receipt. The response must specifically admit or deny that a violation of this part has occurred.
(1)If you admit that a violation has occurred, you must provide to the complainant a written statement setting forth a summary of the facts and the steps, if any, you will take in response to the violation.
(2)If you deny that a violation has occurred, your response must include a summary of the facts and your reasons, under this part, for the determination.
(3)Your response must also inform the complainant of his or her right to pursue DOT and/or DOJ enforcement action under this part. § 39.107 Where may passengers file complaints?
(a)Any person believing that a PVO has violated any provision of this part may contact the following office for assistance: U.S. Department of Transportation, Departmental Office of Civil Rights, 400 Seventh Street, SW, Washington, DC 20590.
(b)Any person believing that a PVO has violated any provision of this part may also file a complaint with the Disability Rights Section, Civil Rights Division, Department of Justice.
(c)Any person believing that a PVO that receives Federal financial assistance has violated any provision of this part may also file a complaint with the civil rights office of the concerned DOT operating administration.
(d)Requests for assistance and complaints must be filed no later than 180 days after the incident, or after the end of a continuing violation, to ensure that they can be investigated. § 39.109 What enforcement action may be taken under this part?
(a)The Department of Transportation may investigate complaints and conduct reviews or other inquiries into the compliance of PVOs with this part.
(b)The Department may issue and make public findings and recommendations concerning any matter relating to the compliance of PVOs with this part.
(c)The Department may refer any matter concerning the compliance of PVOs with this part to the Department of Justice for enforcement action.
(d)The Department of Justice may conduct investigations and take enforcement action concerning compliance with the provisions of this part on its own initiative at any time.
(e)With respect to a PVO that receives DOT financial assistance, the Department may take enforcement action as provided in 49 CFR Parts 27 and 37. [FR Doc. E7-362 Filed 1-22-07; 8:45 am] BILLING CODE 4910-22-P 72 14 Tuesday, January 23, 2007 Notices DEPARTMENT OF AGRICULTURE Food Safety and Inspection Service [Docket No. FSIS-2006-0043] Notice of Request for a Revision of an Information Collection (Pathogen Reduction/Hazard Analysis and Critical Control Point) AGENCY: Food Safety and Inspection Service, USDA. ACTION: Notice and request for comments. SUMMARY: In accordance with the Paperwork Reduction Act of 1995 and the Office of Management and Budget
(OMB)regulations, this notice announces that the Food Safety and Inspection Service
(FSIS)intends to request a revision of an approved information collection on Pathogen Reduction and Hazard Analysis and Critical Control Point (HACCP) Systems. DATES: Comments on this notice must be received on or before March 26, 2007. ADDRESSES: FSIS invites interested persons to submit comments on this notice. Comments may be submitted by any of the following methods: • *Mail, including floppy disks or CD-ROM's, and hand- or courier-delivered items:* Send to Docket Clerk, U.S. Department of Agriculture, Food Safety and Inspection Service, 300 12th Street, SW., Room 102 Cotton Annex, Washington, DC 20250. • *Electronic mail: fsis.regulationscomments@fsis.usda.gov.* • *Federal eRulemaking Portal:* This Web page provides the ability to type short comments directly into the comment field on this Web page or attach a file for lengthier comments. Go to *http://www.regulation.gov* and in the “Search for Open Regulations” box, select “Food Safety and Inspection Service” from the agency drop-down menu, then click on “Submit.” In the Docket ID column, select FDMS Docket Number FSIS-2006-0043 to submit or view public comments and to view supporting and related materials available electronically. All submissions received by mail or electronic mail must include the Agency name and docket number. All comments submitted in response to this document, as well as research and background information used by FSIS in developing this document, will be available for public inspection in the FSIS Docket Room at the address listed above between 8:30 a.m. and 4:30 p.m., Monday through Friday, except Federal holidays. Comments will also be posted on the Agency's Web page at *http://www.fsis.usda.gov/regulations_&_policies/regulations_directives_&_notices/index.asp.* FOR ADDITIONAL INFORMATION: Contact John O'Connell, Paperwork Reduction Act Coordinator, Food Safety and Inspection Service, USDA, 300 12th 7Street, SW., Room 112, Washington, DC 20250-3700,
(202)720-0345. SUPPLEMENTARY INFORMATION: *Title:* Pathogen Reduction/HACCP Systems. *OMB Number:* 0583-0103. *Expiration Date:* 6/30/2007. *Type of Request:* Revision of a currently approved information collection. *Abstract:* FSIS has been delegated the authority to exercise the functions of the Secretary as specified in the Federal Meat Inspection Act
(FMIA)(21 U.S.C. 601, *et seq.* ) and the Poultry Products Inspection Act
(PPIA)(21 U.S.C. 451, *et seq.* ). These statutes provide that FSIS is to protect the public by verifying that meat and poultry products are safe, wholesome, unadulterated, and properly labeled and packaged. FSIS is requesting a revision to an approved information collection addressing paperwork and recordkeeping requirements regarding Pathogen Reduction and HACCP systems. The Agency is revising the Pathogen Reduction/HACCP systems information collection based on its most recent plant data, which support a finding of fewer total burden hours than there is in the currently approved information collection. FSIS has established requirements applicable to meat and poultry establishments designed to reduce the occurrence and numbers of pathogenic microorganisms on meat and poultry products, reduce the incidence of foodborne illness associated with the consumption of those products, and provide a new framework for modernization of the meat and poultry inspection system. The regulations
(1)require that each establishment develop and implement written sanitation standard operating procedures (Sanitation SOPs);
(2)require regular microbial testing for generic *E. coli* by slaughter establishments to verify the adequacy of the establishment's process controls for the prevention and removal of fecal contamination and associated bacteria;
(3)establish pathogen reduction performance standards for *Salmonella* that slaughter establishments and establishments producing raw ground products must meet; and
(4)require that all meat and poultry establishments develop and implement a system of preventive controls designed to improve the safety of their products, known as HACCP. FSIS has made the following estimates based upon an information collection assessment: *Estimate of Burden:* FSIS estimates that it will take respondents an average of .116 hours to comply with the Pathogen Reduction and HACCP systems information collection. *Respondents:* Meat and poultry establishments. *Estimated No. of Respondents:* 7,721. *Estimated No. of Annual Responses per Respondent:* 7,244. *Estimated Total Annual Burden on Respondents:* 6,505,024 hours. Copies of this information collection assessment can be obtained from John O'Connell, Paperwork Reduction Act Coordinator, Food Safety and Inspection Service, USDA, 300 12th Street, SW., Room 112, Washington, DC 20250-3700,
(202)720-5627,
(202)720-0345. *Comments are invited on:*
(a)Whether the proposed collection of information is necessary for the proper performance of FSIS' functions, including whether the information will have practical utility;
(b)the accuracy of FSIS' estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;
(c)ways to enhance the quality, utility, and clarity of the information to be collected; and,
(d)ways to minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques, or other forms of information technology. Comments may be sent to both John O'Connell, Paperwork Reduction Act Coordinator, at the address provided above, and the Desk Officer for Agriculture, Office of Information and Regulatory Affairs, Office of Management and Budget, Washington, DC 20253. All responses to this notice will be summarized and included in the request for OMB approval. All comments will also become a matter of public record. Additional Public Notification Public awareness of all segments of rulemaking and policy development is important. Consequently, in an effort to ensure that the public and in particular minorities, women, and persons with disabilities, are aware of this notice, FSIS will announce it on-line through the FSIS web page located at *http://www.fsis.usda.gov/regulations/2007_Notices_Index/index.asp* . FSIS also will make copies of this **Federal Register** publication available through the FSIS Constituent Update, which is used to provide information regarding FSIS policies, procedures, regulations, **Federal Register** notices, FSIS public meetings, recalls, and other types of information that could affect or would be of interest to our constituents and stakeholders. The update is communicated via Listserv, a free e-mail subscription service consisting of industry, trade, and farm groups, consumer interest groups, allied health professionals, scientific professionals, and other individuals who have requested to be included. The update also is available on the FSIS Web page. Through Listserv and the Web page, FSIS is able to provide information to a much broader, more diverse audience. In addition, FSIS offers an email subscription service which provides automatic and customized access to selected food safety news and information. This service is available at *http://www.fsis.usda.gov/news_and_events/email_subscription/* Options range from recalls to export information to regulations, directives and notices. Customers can add or delete subscriptions themselves and have the option to password protect their account. Done at Washington, DC, on January 17, 2007. Barbara J. Masters, Administrator. [FR Doc. E7-949 Filed 1-22-07; 8:45 am] BILLING CODE 3410-DM-P DEPARTMENT OF AGRICULTURE Grain Inspection, Packers and Stockyards Administration Proposed Posting, Posting, and Deposting of Stockyards AGENCY: Grain Inspection, Packers and Stockyards Administration, USDA. ACTION: Notice and request for comments. SUMMARY: This notice announces several actions related to posting of stockyards; when required we physically post a sign providing public notice that the stockyard is subject to provisions of the Packers and Stockyards Act. We propose to post 10 stockyards. We have received information that these stockyards meet the definition of a stockyard under the Packers and Stockyards Act and, therefore, need to be posted. Posted stockyards are subject to the provisions of the Packers and Stockyards Act. In addition, we have posted 12 stockyards that were previously announced as proposed postings. We determined that the stockyards meet the definition of a stockyard under the Packers and Stockyards Act and, therefore, have been posted. Three other facilities, for which notices of proposed posting were announced, were not posted because they no longer meet the definition of a stockyard. These facilities were either abandoned or underwent a change so they no longer function as a stockyard. We are also deposting two stockyards. These facilities can no longer be used as stockyards and, therefore, are no longer required to be posted. DATES: For the proposed posting of stockyards, we will consider comments that we receive by February 7, 2007. For the deposted stockyards, the deposting is effective on January 23, 2007. ADDRESSES: We invite you to submit comments on this notice. You may submit comments by any of the following methods: • *E-Mail:* Send comments via electronic mail to *comments.gipsa@usda.gov.* • *Mail:* Send hardcopy written comments to H. Tess Butler, GIPSA, USDA, 1400 Independence Avenue, SW., Room 1647-S, Washington, DC 20250-3604. • *Fax: Send comments by facsimile transmission to:*
(202)690-2755. • *Hand Delivery or Courier: Deliver comments to:* H. Tess Butler, GIPSA, USDA, 1400 Independence Avenue, SW., Room 1647-S, Washington, DC 20250-3604. • *Federal eRulemaking Portal:* Go to *http://www.regulations.gov.* Follow the on-line instructions for submitting comments. SUPPLEMENTARY INFORMATION: The Grain Inspection, Packers and Stockyards Administration (GIPSA) administers and enforces the Packers and Stockyards Act of 1921, (7 U.S.C. 181-229) (P&S Act). The P&S Act prohibits unfair, deceptive, and fraudulent practices by livestock market agencies, dealers, stockyard owners, meat packers, swine contractors, and live poultry dealers in the livestock, poultry, and meatpacking industries. Section 302 of the P&S Act (7 U.S.C. 202) defines the term “stockyard” as follows: * * * any place, establishment, or facility commonly known as stockyards, conducted, operated, or managed for profit or nonprofit as a public market for livestock producers, feeders, market agencies, and buyers, consisting of pens, or other inclosures, and their appurtenances, in which live cattle, sheep, swine, horses, mules, or goats are received, held, or kept for sale or shipment in commerce. Section 302
(b)of the P&S Act requires the Secretary to determine which stockyards meet this definition, and to notify the owner of the stockyard and the public of that determination by posting a notice in each designated stockyard. After giving notice to the stockyard owner and to the public, the stockyard will be subject to the provisions of Title III of the P&S Act (7 U.S.C. 201-203 and 205-217a) until the Secretary deposts the stockyard by public notice. This document notifies the stockyard owners and the public that the following 10 stockyards meet the definition of a stockyard and that we propose to designate these stockyards as posted stockyards. Facility number Stockyard name and location AL-193 Tim White d.b.a. 4/W Horse Sales, Huntsville, Alabama. AL-194 Coffee County Stockyard, LLC, New Brockton, Alabama. AR-178 B-B Livestock Auction & Sales, Inc., Beebe, Arkansas. AR-179 Buddy Guyot d.b.a. Beebe Livestock Auction, Beebe, Arkansas. GA-230 Frank Ray Harris d.b.a. Harris Goat 'N Sheep Auction, Taylorsville, Georgia. KY-180 Southern Kentucky Livestock Market, Inc., Rockfield, Kentucky. KY-181 Wigwam Livestock Market, Inc., Horse Cave, Kentucky. MO-287 Springfield Livestock Marketing Center, LLC, Springfield, Missouri. PA-162 John H. Wetmore, Honesdale, Pennsylvania. SD-171 SFRL, Inc., d.b.a. Sioux Falls Regional Livestock, Worthing, South Dakota. This document also notifies the public that the following stockyards meet the definition of a stockyard and that we have posted the stockyards. We published notices proposing to post these 12 stockyards on August 25, 2003, July 6, 2004, July 25, 2005, and April 5, 2006 (68 FR 51005, 69 FR 40597-40598, 70 FR 42532-42533, and 71 FR 17071-17072, respectively). We received no comments in response to these proposed posting notices. To post a stockyard, we assign the stockyard a facility number, notify the owner of the stockyard facility, and send notices to the owner of the stockyard to post on display in public areas of the stockyard. The date of posting is the date on which the posting notices are physically displayed. Facility number Stockyard name and location Date of posting FL-139 Arcadia Stockyard, Arcadia, Florida May 3, 2006. GA-228 Triple R Ranch, Lavonia, Georgia June 27, 2006. GA-229 Red Barn Livestock Auction, Inc., Sylvester, Georgia August 22, 2006. LA-147 Hays Brothers Livestock Market, LLC, Arcadia, Louisiana May 11, 2006 MO-286 Miller County Regional Stockyards, Eldon, Missouri May 23, 2006. NC-177 Cliffside Horse Auction, Mooresboro, North Carolina October 6, 2006. NY-174 Woods Auction Service, Cincinnatus, New York May 4, 2006. PA-160 Beach's Dairy Auction, Martinsburg, Pennsylvania May 30, 2006. PA-161 Jonas Lee Fisher & Jacob B. Fisher d.b.a. Fisher's Quality Dairy Sales, Ronks, Pennsylvania October 19, 2006. TX-348 Grimes County Stockyards, LLC, Navasota, Texas May 8, 2006. WI-148 Milwaukee Stockyards, LLC, Reeseville, Wisconsin July 24, 2006. WI-149 Horst Stables, LLC, Thorp, Wisconsin July 15, 2006. This document also notifies the public that the following facilities, which previously met the definition of a stockyard, were not posted. We published notices proposing to post these three stockyards on July 25, 2005, and April 5, 2006 (70 FR 42532-42533 and 71 FR 17071-17072, respectively). The facilities were not posted because they no longer meet the definition of a stockyard. The facilities were either abandoned or underwent a change so that they no longer function as a stockyard. Facility number Stockyard name and location AR-177 Morrilton Horse Sale, Morrilton, Arkansas. GA-227 Friendship Farm Livestock Auction, Bartow, Georgia. IN-168 Hardinsburg Horse Sales, Hardinsburg, Indiana. Additionally, this document notifies the public that the following two stockyards no longer meet the definition of a stockyard and that we are deposting them. We depost stockyards when the facility can no longer be used as a stockyard. Some of the reasons a facility can no longer be used as a stockyard include: the market agency has moved and the posted facility is abandoned, the facility has been torn down or otherwise destroyed, such as by fire, the facility is dilapidated beyond repair, or the facility has been converted and its function changed. Facility number Stockyard name and location Date posted ID-118 Rexburg Livestock Company, Rexburg, Idaho April 3, 1950. WA-112 Marysville Livestock Auction, Inc., Marysville, Washington February 27, 1962. Effective Date These depostings are effective upon publication in the **Federal Register** because they relieve a restriction and, therefore, may be made effective in less than 30 days after publication in the **Federal Register** without prior notice or other public procedure. Authority: 7 U.S.C. 202. James E. Link, Administrator, Grain Inspection, Packers and Stockyards Administration. [FR Doc. 07-257 Filed 1-22-07; 8:45 am]
Connectionstraces to 38
Traces to 38 documents
U.S. Code
43 references not yet in our index
  • 21 CFR 101
  • Pub. L. 108-282
  • 5 USC 601-612
  • Pub. L. 104-4
  • 28 CFR 20
  • Pub. L. 108-277
  • 18 USC 926C(d)
  • Pub. L. 92-544
  • 86 Stat. 1115
  • Pub. L. 99-169
  • Pub. L. 99-569
  • Pub. L. 101-410
  • 104 Stat. 890
  • Pub. L. 104-134
  • 20 CFR 20.33(a)(1)
  • 32 CFR 311
  • Pub. L. 96-354
  • Pub. L. 96-511
  • Pub. L. 93-579
  • 88 Stat. 1986
  • 5 USC 522a
  • 40 CFR 52
  • 44 CFR 67
  • 44 CFR 67.4(a)
  • 44 CFR 60.3
  • 44 CFR 10
  • 49 CFR 39
  • 28 CFR 36
  • 545 U.S. 119
  • 14 CFR 382.40(a)
  • 14 CFR 382.40(b)
  • 49 CFR 27
  • 14 CFR 382.70
  • 13 CFR 121
  • Pub. L. 101-336
  • 104 Stat. 327
  • 42 USC 12101-12213
  • Pub. L. 93-112
  • 87 Stat. 394
  • 49 CFR 38
+ 3 more
Citation graph
cites case law
Proposed Rules
Proposed rule
Fed. Reg.Proposed Rules
C.F.R.§ 101.60
C.F.R.§ 101.61
C.F.R.§ 101.62
U.S.C.§ 343
C.F.R.§ 101.13
Fed. Reg.Notices
C.F.R.§ 25.30
U.S.C.§ 1453
SCOTUS545 U.S. 119
Cite21 CFR 101
Pub. L.Pub. L. 108-282
Cites 81 · showing 12Cited by 0 across 0 sources
★   the supreme law of the land   ★
Don't Tread on Me
E Pluribus Unum — out of many, one

"If you don't know your rights, you don't have any."

Marginalia · a citizen's law index
A research desk, not legal advice. Always read the cited source before relying on a summary.
Questions or an issue? support@self-law.org
disclaimerMarginalia is a research index, not a law firm. Nothing on this site is legal, tax, or financial advice and no attorney–client relationship is formed by using it. Statutes, regulations, and case law change; summaries, search results, AI output, and member posts may be incomplete, out of date, or wrong. Any interpretation drawn from material on this site should be validated by a licensed attorney in your jurisdiction before you act on it.