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.

Code · REGISTER · 2007-12-28 · Federal Highway Administration (FHWA), DOT · Notices

Notices. Notice of request for extension of currently approved information collection

23,928 words·~109 min read·/register/2007/12/28/07-6235

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

BILLING CODE 4910-13-M DEPARTMENT OF TRANSPORTATION Federal Highway Administration [Docket No. FHWA-2007-0030] Agency Information Collection Activities: Notice of Request for Extension of Currently Approved Information Collection AGENCY: Federal Highway Administration (FHWA), DOT. ACTION: Notice of request for extension of currently approved information collection. SUMMARY: The FHWA has forwarded the information collection request described in this notice to the Office of Management and Budget
(OMB)for approval of an extension of a currently approved information collection. We published a **Federal Register.** Notice with a 60-day public comment period on this information collection on August 17, 2007. We are required to publish this notice in the **Federal Register** by the Paperwork Reduction Act of 1995. DATES: Please submit comments by January 28, 2008. ADDRESSES: You may send comments within 30 days to the Office of Information and Regulatory Affairs, Office of Management and Budget, 725 17th Street, NW., Washington, DC, 20503, or e-mail at *oira_submission@omb.eop.gov* , Attention DOT Desk Officer. You are asked to comment on any aspect of this information collection, including:
(1)Whether the proposed collection is necessary for the FHWA's performance;
(2)the accuracy of the estimated burden;
(3)ways for the FHWA to enhance the quality, usefulness, and clarity of the collected information; and
(4)ways that the burden could be minimized, including the use of electronic technology, without reducing the quality of the collected information. All comments should include the Docket number FHWA-2007-0030. FOR FURTHER INFORMATION CONTACT: For information regarding Emergency Relief Funding Applications, contact Greg Wolf, 202-366-4655, Office of Program Administration, Federal Highway Administration, Department of Transportation, 1200 New Jersey Ave., SE., Washington, DC 20590. Office hours are from 7:30 a.m. to 4:30 p.m., Monday through Friday, except Federal holidays. SUPPLEMENTARY INFORMATION: *Title:* Emergency Relief Funding Applications. *Background:* Section 125 of Title 23 United States Code requires States to submit applications to the FHWA for emergency relief
(ER)funds. The ER funds are established for the repair or reconstruction of Federal-aid highways and Federally-owned roads, which have suffered serious damage from natural disasters over a wide area or a catastrophic failure from an external cause. The information is needed by the FHWA to fulfill its statutory obligations regarding funding determinations for emergency work to repair damaged highway facilities. The requirements covering the FHWA ER program are contained in 23 CFR Part 668. *Respondents:* 50 State Transportation Departments, the District of Columbia, the Commonwealth of Puerto Rico, the Commonwealth of the Northern Mariana Islands, and the Territories of Guam, the Virgin Islands and American Samoa. *Frequency:* As required. *Estimated Average Burden per Response:* The estimated burden to complete the application is 250 hours. *Estimated Total Annual Burden Hours:* Approximately 7,500 hours annually. *Electronic Access:* Internet users may access all comments received by the U.S. DOT Dockets, Room PL-401, by using the universal resource locator (URL): *http://dms.dot.gov,* 24 hours each day, 365 days each year. Please follow the instructions online for more information and help. Authority: The Paperwork Reduction Act of 1995; 44 U.S.C. Chapter 35, as amended; and 49 CFR 1.48. Issued on: December 20, 2007. James R. Kabel, Chief, Management Programs and Analysis Division. [FR Doc. E7-25131 Filed 12-27-07; 8:45 am] BILLING CODE 4910-22-P DEPARTMENT OF TRANSPORTATION Federal Highway Administration [Docket No. FHWA-2007-0031] Agency Information Collection Activities: Notice of Request for Extension and Change of Title of a Currently Approved Information Collection AGENCY: Federal Highway Administration (FHWA), DOT. ACTION: Notice of request for extension and change of title of a currently approved information collection. — SUMMARY: The FHWA has forwarded the information collection request described in this notice to the Office of Management and Budget
(OMB)for approval of an extension and change of title of a currently approved information collection. We published a **Federal Register** Notice with a 60-day public comment period on this information collection on August 31, 2007. We are required to publish this notice in the **Federal Register** by the Paperwork Reduction Act of 1995. As part of FHWA's ongoing effort to reduce the overall burden on the public, four information collections associated with the accommodation or relocation of utility facilities in the right-of-way of highway facilities are being combined into a single collection (2125-0519) with a new title of Utility Adjustments, Agreements, Eligibility Statements, and Accommodation Policies. The four affected information collections are: 2125-0514: Develop and Submit Utility Accommodation Policies; 2125-0515: Eligibility Statement for Utility Adjustments; 2125-0519: Developing and Recording Costs for Utility Adjustments; and 2125-0522: Utility Use and Occupancy Agreements. DATES: Please submit comments by January 28, 2008. ADDRESSES: You may send comments within 30 days to the Office of Information and Regulatory Affairs, Office of Management and Budget, 725 17th Street, NW, Washington, DC, 20503, or e-mail at *oira_submission@omb.eop.gov* , Attention DOT Desk Officer. You are asked to comment on any aspect of this information collection, including:
(1)Whether the proposed collection is necessary for the FHWA's performance;
(2)the accuracy of the estimated burden;
(3)ways for the FHWA to enhance the quality, usefulness, and clarity of the collected information; and
(4)ways that the burden could be minimized, including the use of electronic technology, without reducing the quality of the collected information. All comments should include the Docket number FHWA-2007-0031. FOR FURTHER INFORMATION CONTACT: Mr. Jon Obenberger, 202-366-2221, Office of Infrastructure, Federal Highway Administration, Department of Transportation, 1200 New Jersey Avenue, SE., Washington, DC 20590. Office hours are from 8 a.m. to 4:30 p.m., Monday through Friday, except Federal holidays. SUPPLEMENTARY INFORMATION: *Title:* Utility Adjustments, Agreements, Eligibility Statements, and Accommodation Policies; formerly titled “Developing and Recording Costs for Utility Adjustments.” *Background:* Federal laws dealing with the relocation and accommodation of utility facilities associated with the right-of-way of highway facilities are contained in the United States Code (U.S.C.) 23, Sections 123 and 109(I)(1). Regulations dealing with the utility facility accommodation and relocation are based upon the laws contained in 23 U.S.C. and are found in the Code of Federal Regulations (CFR), Title 23, Chapter I, Subchapter G, Part 645, subparts A and B. The FHWA requires (23 CFR 645 subpart A—Utility Relocations, Adjustments, and Reimbursement) developing and recording costs for utility adjustments, as the basis for reimbursing State Departments of Transportation (SDOTs) and local agency transportation departments, when they have paid the costs of utility facilities relocations that were required by the construction of Federal-aid highway projects. The FHWA requires the utility companies to document the costs or expenses for adjusting their facilities. These utility companies must have a system for recording labor, materials, supplies and equipment costs incurred when undertaking adjustments to accommodate the highway projects. This record of costs forms the basis for payment by the SDOT or local transportation department to the utility company. In turn the FHWA reimburses the SDOT or local transportation department for its payment to the utility company. The utility company is required to maintain these records of costs for 3 years after final payment is received. The SDOT and/or local agency transportation departments are responsible for maintaining the highway rights-of-way, including the control of its use by the utility companies. In managing the use of the highway rights-of-way, the SDOT and/or local agency transportation department is required (23 CFR 645.205 and 23 CFR 645.213) to document the terms under which utility facilities are allowed to cross or otherwise occupy the highway rights-of-way, in the form of utility use and occupancy agreements (formerly OMB Control #: 2125-0522) with each utility company. This documentation, consisting of a use and occupancy agreement (permit), must be in writing and must be maintained in the SDOT and/or local agency transportation department. Each SDOTs is required (23 CFR 615.215) to submit to the FHWA a utility adjustment eligibility statement (formerly OMB Control #: 2125-0515) that establishes the SDOT's legal authority and policies it employs for accommodating utilities within highway rights-of-way or obligation to pay for utility adjustments. FHWA has previously reviewed and approved these eligibility statements for each State DOT. The statements are used as a basis for Federal-aid reimbursement in utility relocation costs under the provisions of 23 U.S.C. 123. Updated statements may be submitted for review at the States discretion where circumstances have modified (for example, a change in State statute) the extent to which utility adjustments are eligible for reimbursement by the State or those instances where a local SDOT's legal basis for payment of utility adjustments differs from that of the State. Each SDOT is also required (23 CFR 645.215) to develop and submit to FHWA their utility accommodation policies (formerly OMB Control #: 2125-0514) that will be used to regulate and manage the utility facilities within the rights-of-way of Federal-aid highway projects. The agencies utility accommodation policies need to address the basis for utility facilities to use and occupy highway rights-of-way; the State's authority to regulate such use; and the policies and/or procedures employed for managing and accommodating utilities within the rights-of-way of Federal-aid highway projects. Upon FHWA's approval of the policy statement, the SDOT may take any action required in accordance with the approved policy statement without a case-by-case review by the FHWA. In addition, the utility accommodation policy statements that have been approved previously by the FHWA are periodically reviewed by the SDOTs to determine if updating is necessary to reflect policy changes. *Respondents:* 52 SDOTs, including the District of Columbia and Puerto Rico, local agency transportation departments, and utility companies. *Frequency:* The SDOTs and local agency transportation departments are each involved in an average of 15 utility use and occupancy agreements (or permits) per year for an annual frequency of 46,000. SDOTs are allowed to submit their eligibility statement for utility adjustments and their utility accommodation policies when warranted by changes or when updates occur, or at the SDOT's discretion. It is estimated 10 SDOTs will update either their eligibility statement for utility agreements or utility accommodation policies per year. *Estimated Average Burden per Response:* The estimated average amount of time required to develop and record the costs for each utility adjustment is 8 hours. The estimated amount of time required by the SDOTs and local agency transportation departments to process each utility use and occupancy agreement (permit) is 8 hours. The estimated amount of time for each update to the SDOT's eligibility statement for utility adjustments has an average burden of 18 hours. The estimated amount of time for each update and submittal of a SDOT's utility accommodation policy has an average burden of 280 hours. *Estimated Total Annual Burden Hours:* The annual burden associated with developing and recording the costs for adjusting utility facilities is 72,000 hours based on an estimate of 9,000 adjustments that utility companies perform annually that may be eligible for Federal-aid highway funding allowing SDOTs or local agency transportation departments to request reimbursement from FHWA. The annual burden associated with preparing, submitting and approving utility use and occupancy agreements (permits) is 552,000 burden-hours. The annual burden associated with developing and approving updates to a SDOT's eligibility statement for utility adjustments is 90 hours. The annual burden associated with developing and approving updates to SDOTs' utility accommodation policies is 1,400 hours. The accumulated burden for the combined information collection is 625,490. *Electronic Access:* Internet users may access all comments received by the U.S. DOT Dockets, Room PL-401, by using the universal resource locator (URL): *http://dms.dot.gov,* 24 hours each day, 365 days each year. Please follow the instructions online for more information and help. Authority: The Paperwork Reduction Act of 1995; 44 U.S.C. Chapter 35, as amended; and 49 CFR 1.48. Issued on: December 20, 2007. James R. Kabel, Chief, Management Programs and Analysis Division. [FR Doc. E7-25205 Filed 12-27-07; 8:45 am] BILLING CODE 4910-22-P DEPARTMENT OF TRANSPORTATION Federal Railroad Administration Petition for a Waiver of Compliance In accordance with Title 49 Code of Federal Regulations
(CFR)§§ 211.9 and 211.41, notice is hereby given that the Federal Railroad Administration
(FRA)received a request for a waiver of compliance with certain requirements of its safety standards. The individual petition is described below, including the party seeking relief, the regulatory provisions involved, the nature of the relief being requested, and the petitioner's arguments in favor of relief. Canadian Pacific Railway [Waiver Petition Docket Number FRA-2007-0008] The Canadian Pacific Railway
(CP)seeks a waiver from the requirements of 49 CFR 240.117(e)(1) through (4), 240.305, and 240.307, in connection with implementation of a Close Call Reporting System
(C3RS)Demonstration Pilot Project (Pilot Project) sponsored by FRA's Office of Research and Development. These sections of the regulation relate to punitive actions that are required to be taken against locomotive engineers for the violation of certain railroad operating rules. Refer to Part 240 for a detailed listing of these sections. CP and the employees of CP's Chicago Service Area, represented by the Brotherhood of Locomotive Engineers and Trainmen
(BLET)and the United Transportation Union (UTU), desire to participate in the Pilot Project, which is one of the action items included in FRA's Action Plan for Addressing Critical Railroad Safety Issues (Action Plan) announced on January 25, 2006. As noted in the Action Plan, in other industries such as aviation and mining, as well as in the European railway industry, implementation of “close call” reporting systems that shield the reporting employee from discipline (and the employer from punitive sanctions levied by the regulation) have contributed to major reductions in accidents. In March of 2005, FRA completed an overarching memorandum of understanding with railroad labor organizations and management to develop pilot programs to document close calls, i.e., unsafe events that do not result in a reportable accident but very well could have. Participating railroads will be expected to develop corrective actions to address the problems that may be revealed. The aggregate data may prove useful in FRA's decision-making concerning regulatory and other options to address human factor-caused accidents. CP, BLET, and UTU have developed and signed an implementing memorandum of understanding (IMOU), based on the FRA's overarching memorandum of understanding, as a first step in commencing the demonstration pilot project. The project would involve approximately 350 yard and road service employees operating between Newport, Minnesota, (Mile Post
(MP)402.5C, River Subdivision) and Tower A-20 (MP 20.5, C&M Subdivision), and all track between those mileposts, including track on the following subdivisions: River, Tomah, Watertown, M&P, the CN Valley, and C&M. This IMOU was sent to FRA for consideration and acceptance on October 8, 2007. As referenced in the IMOU, certain “close calls” may be properly reported by the employee(s) involved and later discovered by CP, for example, through subsequent retrospective analysis of locomotive event recorder data, etc. In order to encourage employee reporting of close calls, the IMOU contains provisions to shield the reporting employee from CP discipline. CP, BLET, and UTU also desire to shield the reporting employee(s) and CP from punitive sanctions that would otherwise arise as provided in selected sections of Part 240 for properly reported close call events as defined in the C3RS IMOU. The waiver petition is requested for the duration of the C3RS Pilot Project (5 years from implementation or until the Pilot Project is completed or parties to the IMOU withdraw as described in the IMOU, whichever comes first). Note: According to Article 7.2 of the IMOU, “Conditions under which a reporting employee is not protected from CP discipline and/or decertification and from FRA enforcement,” CP employees included in this C3RS/IMOU receive no protection from discipline and/or decertification or from FRA enforcement action when one or more of the following conditions occur: • The employee's action or lack of action was intended to damage CP or another entity's operations or equipment, or to injure other individuals or purposely place others in danger (e.g., sabotage); • The employee's action or lack of action involved a criminal offense; • The employee's behavior involved substance abuse or inappropriate use of controlled substances; • The report is rejected by the Bureau of Transportation Statistics Peer Review Team; • The event resulted in a railroad accident/incident that qualifies as reportable under § 225.11; • The event resulted in an identifiable release of a hazardous material; or • The event was observed in real-time and reported to CP management (such as a train dispatcher or operator observing a signal violation) or was observed as part of proficiency testing. Proficiency testing (e.g., operating rule efficiency testing, signal compliance testing) generally consists of real-time observations and do not qualify for exemption. Similarly, an employee is not exempt from discipline and/or decertification for a violation that CP or FRA identifies contemporaneously (e.g., a block circuit is occupied by a train without authority, and the train dispatcher notices it before the train backs off the circuit) before the employee files a close call report. In such situations, CP or FRA may use event recorder information to support discipline and/or decertification and/or enforcement. For example, a CP official who observes a train operate past a signal that requires a stop may use any relevant data recorded by the locomotive's event recorder in pursuing disciplinary action against the train crew, regardless of whether a member of the crew timely files a close call report. In its petition, CP indicated that the parties signatory to the IMOU, dated August 21, 2007, believe the data from these properly reported close call incidents, as defined in the IMOU, will be invaluable in the analysis and development of effective corrective actions. CP expressed the view that without the requested waiver the employee(s) involved in incidents such as those described above will not file reports of the incidents and that the incident(s) will likely go undetected, resulting in no opportunity for analysis, data trending, or appropriate corrective actions. Noting the success of close call reporting systems in other industries (e.g., aviation and maritime), CP further indicated that all parties signatory to the IMOU and participating in the Pilot Project believe that the Pilot Project and requested regulatory relief is in the public interest and consistent with railroad safety. Interested parties are invited to participate in these proceedings by submitting written views, data, or comments. FRA does not anticipate scheduling a public hearing in connection with these proceedings since the facts do not appear to warrant a hearing. If any interested party desires an opportunity for oral comment, they should notify FRA in writing, before the end of the comment period and specify the basis for their request. All communications concerning these proceedings should identify the appropriate docket number (e.g., Waiver Petition Docket Number FRA-2007-0008) and may be submitted by any of the following methods: • *Web site: http://www.regulations.gov* . Follow the online instructions for submitting comments. • *Fax:*
(202)493-2251. • *Mail:* Docket Operations Facility, U.S. Department of Transportation, 1200 New Jersey Avenue, SE., W12-140, Washington, DC 20590. • *Hand Delivery:* 1200 New Jersey Avenue, SE., Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. Communications received within 45 days of the date of this notice will be considered by FRA before final action is taken. Comments received after that date will be considered as far as practicable. All written communications concerning these proceedings are available for examination during regular business hours (9 a.m.-5 p.m.) at the above facility. All documents in the public docket are also available for inspection and copying on the Internet at the docket facility's Web site at *http://www.regulations.gov* . Anyone is able to search the electronic form of any written communications and comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT's complete Privacy Act Statement in the **Federal Register** published on April 11, 2000 (Volume 65, Number 70; Pages 19477-78). Issued in Washington, DC, on December 19, 2007. Grady C. Cothen, Jr., Deputy Associate Administrator for Safety Standards and Program Development. [FR Doc. E7-25141 Filed 12-27-07; 8:45 am] BILLING CODE 4910-06-P DEPARTMENT OF TRANSPORTATION Federal Railroad Administration Petition for Waiver of Compliance In accordance with Part 211 of Title 49 Code of Federal Regulations (CFR), notice is hereby given that the Federal Railroad Administration
(FRA)received a request for a waiver of compliance with certain requirements of its safety standards. The individual petition is described below, including the party seeking relief, the regulatory provisions involved, the nature of the relief being requested, and the petitioner's arguments in favor of relief. Durbin & Greenbrier Valley Railroad [Waiver Petition Docket Number FRA-2007-27868] The Durbin & Greenbrier Valley Railroad, Inc. (DGVR), a Class III railroad, seeks a waiver of compliance from the requirements of CFR § 223.11 *Requirements for existing locomotives* for Locomotive Number 82. Specifically, DGVR petitioned FRA for a waiver for a 1,500 horsepower diesel electric locomotive, model BL-2, built by the Electro Motive Division of General Motors in 1948. This locomotive is on loan from the State of West Virginia
(WV)Rail Authority. The locomotive is stored in Belington, WV, and operated by a subsidiary division of DGVR, the West Virginia Central. Locomotive Number 82 is used on a limited basis for freight and excursion passenger service from a station in Hi Falls, WV (Milepost
(MP)51) to Tygart Junction, WV (MP 0.02), approximately 50 miles. There are 21 highway/rail crossings at grade, and two overpasses. One is located in Elkins, WV, and the other approximately 10 miles east of Elkins. The railroad operates through rural and relatively unpopulated areas, and there have been no reports of glazing vandalism along this right-of-way. The petitioner believes that this locomotive can be safely operated throughout the rural area with the current non-compliant safety-type glazing. The cost to DGVR for installation of all new window frames and compliant FRA Types I & II glazing is significant, with only a marginal increase in safety due to the low speed. Interested parties are invited to participate in these proceedings by submitting written views, data, or comments. FRA does not anticipate scheduling a public hearing in connection with these proceedings since the facts do not appear to warrant a hearing. If any interested party desires an opportunity for oral comment, they should notify FRA, in writing, before the end of the comment period and specify the basis for their request. All communications concerning these proceedings should identify the appropriate docket number (e.g., Waiver Petition Docket Number FRA-2007-27868) and may be submitted by any of the following methods: *Web site: http://www.regulations.gov.* Follow the online instructions for submitting comments. *Fax:* 202-493-2251. *Mail:* Docket Operations Facility, U.S. Department of Transportation, 1200 New Jersey Avenue, SE., W12-140, Washington, DC 20590. *Hand Delivery:* 1200 New Jersey Avenue, SE., Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal Holidays. Communications received within 45 days of the date of this notice will be considered by FRA before final action is taken. Comments received after that date will be considered as far as practicable. All written communications concerning these proceedings are available for examination during regular business hours (9 a.m.-5 p.m.) at the above facility. All documents in the public docket are also available for inspection and copying on the Internet at the docket facility's Web site at *http://www.regulations.gov.* Anyone is able to search the electronic form of any written communications and comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT's complete Privacy Act Statement in the **Federal Register** published on April 11, 2000 (Volume 65, Number 70; Pages 19477-78). Issued in Washington, DC, on December 19, 2007. Grady C. Cothen, Jr., Deputy Associate Administrator for Safety Standards and Program Development. [FR Doc. E7-25069 Filed 12-27-07; 8:45 am] BILLING CODE 4910-06-P DEPARTMENT OF TRANSPORTATION Federal Railroad Administration Notice of Informational Filing In accordance with § 236.913 of Title 49 of the Code of Federal Regulations (CFR), notice is hereby given that the Federal Railroad Administration
(FRA)has received an informational filing from the Ohio Central Railroad System
(OCRS)to permit field testing of the railroad's processor-based train control system. The informational filing is described below, including the requisite docket number where the informational filing and any related information may be found. The document is also available for public inspection; however, FRA is not accepting public comments. Ohio Central Railroad System [Docket Number FRA-2006-26177] OCRS has submitted an informational filing to FRA to permit field testing of the railroad's processor-based train control system identified as OCRS Positive Train Control (OCRS PTC). The informational filing addresses the requirements under 49 CFR 236.913(j)(1). Specifically, the informational filing contains a description of the OCRS PTC product and an operational concepts document, pursuant to 49 CFR 236.913(j)(1). The OCRS PTC system is designed to prevent authority limit and over-speed violations in non-signaled Track Warrant Control
(TWC)territory, and to prevent equipped trains from entering the limits, without authorization, of on-track authority granted to employees. OCRS desires to commence field testing in the fourth quarter of 2007, or as soon as practicable thereafter, contingent upon FRA's acceptance and approval of their informational filing. Interested parties are invited to review the informational filing and associated documents at the DOT Docket Management facility during regular business hours (9 a.m.—5 p.m.) at 1200 New Jersey Avenue, SE., Room W12-140, Washington, DC 20590. All documents in the public docket are also available for inspection and copying on the internet at *http://www.regulations.gov.* Anyone is able to search the electronic form of any written communications received into any of our dockets by name of the individual submitting the document (or signing the document, if submitted on behalf of an association, business, labor union, etc.). You may review the DOT(s complete Privacy Act Statement in the **Federal Register** published on April 11, 2000 (Volume 65, Number 70; Pages 19477-78). Issued in Washington, DC, on December 19, 2007. Grady C. Cothen, Jr., Deputy Associate Administrator for Safety Standards and Program Development. [FR Doc. E7-25142 Filed 12-27-07; 8:45 am] BILLING CODE 4910-06-P DEPARTMENT OF TRANSPORTATION National Highway Traffic Safety Administration [U.S. DOT Docket Number NHTSA-2007-0049] Reports, Forms, and Recordkeeping Requirements AGENCY: National Highway Traffic Safety Administration (NHTSA), Department of Transportation. ACTION: Request for public comment on a previously approved collection of information. SUMMARY: Before a Federal agency can collect certain information from the public, it must receive approval from the Office of Management and Budget (OMB). Under procedures established by the Paperwork Reduction Act of 1995, before seeking OMB approval, Federal agencies must solicit public comment on proposed collections of information, including extensions and reinstatement of previously approved collections. This document describes one collection of information for Part 565, Parts 567 and Part 541 for which NHTSA intends to seek OMB approval. DATES: Comments must be received on or before February 26, 2008. ADDRESSES: You may submit comments [identified by DOT Docket No. NHTSA-2007-0049] by any of the following methods: • *Federal eRulemaking Portal:* Go to *http://www.regulations.gov* . Follow the online instructions for submitting comments. Web site: *http://dms.dot.gov* . Follow the instructions for submitting comments on the DOT electronic docket site. Alternatively, you can file comments using the following methods: • *Mail:* Docket Management Facility: U.S. Department of Transportation, 1200 New Jersey Avenue, SE., West Building, Ground Floor, Room W12-140, Washington, DC 20590-0001. • *Hand Delivery or Courier:* West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m. ET, Monday through Friday, except Federal holidays. • *Fax:* 1-202-493-2251. *Instructions:* For detailed instructions on submitting comments and additional information on the rulemaking process, see the Public Participation heading of the Supplementary Information section of this document. Note that all comments received will be posted without change to *http://dms.dot.gov* or *http://www.regulations.gov,* including any personal information provided. Please see the Privacy Act heading below. *Privacy Act:* Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT's complete Privacy Act Statement in the **Federal Register** . *Docket:* For access to the docket to read background documents or comments received, go to the street address listed above. The internet access to the docket will be at *http://www.regulations.gov* . Follow the online instructions for accessing the dockets. FOR FURTHER INFORMATION CONTACT: Complete copies of each request for collection of information may be obtained at no charge from Ms. Deborah Mazyck, NHTSA, 1200 New Jersey Avenue, SE., West Building, Room W43-443, Washington, DC 20590. Ms. Mazyck's telephone number is
(202)366-4139 and email address is *Deborah.Mazyck@dot.gov* . Please identify the relevant collection of information by referring to its OMB Control Number. SUPPLEMENTARY INFORMATION: Under the Paperwork Reduction Act of 1995, before an agency submits a proposed collection of information to OMB for approval, it must first publish a document in the **Federal Register** providing a 60-day comment period and otherwise consult with members of the public and affected agencies concerning each proposed collection of information. The OMB has promulgated regulations describing what must be included in such a document. Under OMB's regulation (at 5 CFR 1320.8(d)), an agency must ask for public comment on the following:
(i)Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;
(ii)The accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;
(iii)How to enhance the quality, utility, and clarity of the information to be collected;
(iv)How to minimize the burden of the collection of information on those who are to respond, including the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, e.g. permitting electronic submission of responses. In compliance with these requirements, NHTSA asks for public comments on the following previously approved collection of information: *Title:* Consolidated Labeling Requirements for 49 CFR 541, 565 and 567. *OMB Control Number:* 2127-0510. *Form Number:* None. *Affected Public:* Vehicle manufacturers. *Requested Expiration Date of Approval:* Three years from approval date. *Abstract:* For Parts 565, 541 and 567. Parts 565 and 567 NHTSA's statute at 15 U.S.C. 1392,1397,1401,1407, and 1412 of the National Traffic and Motor Vehicle Safety Act of 1966 authorizes the issuance of Federal Motor Vehicle Safety Standard (FMVSS) and the collection of data which support their implementation. The agency, in prescribing an FMVSS, is to consider available relevant motor vehicle safety data and to consult with other agencies as it deems appropriate. Further, the Act mandates, that in issuing any FMVSS, the agency should consider whether the standard is reasonable, practicable and appropriate for the particular type of motor vehicle or item of motor vehicle equipment for which it is prescribed, and whether such standards will contribute to carrying out the purpose of the Act. The Secretary is authorized to revoke such rules and regulations as deemed necessary to carry out this subchapter. Using this authority, the agency issued the initial FMVSS No. 115, Vehicle Identification Number, specifying requirements for vehicle identification numbers to aid the agency in achieving many of its safety goals. The standard was amended in August 1978 by extending its applicability to additional classes of motor vehicles and by specifying the use of a 30-year, 17-character Vehicle Identification Number
(VIN)for worldwide use. The standard was amended in May 1983 by deleting portions of FMVSS No. 115 and reissuing those portions as a general agency regulation, Part 565. Subsequently, the standard was amended again in June 1996 transferring the text of the FMVSS No. 115 to Part 565, without making any substantive changes to the VIN requirements as a result of the proposed consolidation. The provision of the Part 565 (amended) regulation requires vehicle manufacturers to assign a unique VIN to each new vehicle and to inform NHTSA of the code used in forming the VIN. These regulations apply to all vehicles: passenger cars, multipurpose passenger vehicles, trucks, buses, trailers, incomplete vehicles, and motorcycles. NHTSA has proposed amendments to Part 565 to revise certain sections in order to extend the existing VIN system for another thirty years, and to ensure a sufficient supply of unique available VINs and manufacturer identifiers for that time period (72 FR 56027, October 2, 2007). The agency may require information to be provided in a slightly different way (e.g., vehicle make being transferred from the first to the second section of the VIN), the scope of the overall reporting requirement of Part 565 will not change. The agency does not anticipate an increase or decrease in the collection of information requirements if these proposals are adopted. Part 567 specifies the content and location of, and other requirements for, the certification label or tag to be affixed to motor vehicles and motor vehicle equipment. Specifically, the VIN is required to appear on the certification label. Additionally, this certificate will provide the consumer with information to assist him or her in determining which of the Federal Motor Vehicle Safety Standards are applicable to the vehicle or equipment, and its date of manufacture. NHTSA estimates the vehicle manufacturers will incur a decrease in total annual hour burden of 423,333. The recordkeeping hour burden for Part 565 and 567 represents a decrease in hour burden because of a decrease in the number of respondents. NHTSA estimates an increase in cost burden of $3,400.00. Due to the fluctuation of the U.S. economy, there was an increase in cost to comply with the reporting requirements. The change in cost burden reflects the 2007 Consumer Price Index as compared to that of 1987. Part 541 The Motor Vehicle Information and Cost Savings Act was amended by the Anti-Car Theft Act of 1992 (Pub. L. 102-519). The enacted Theft Act requires specified parts of high-theft vehicle to be marked with vehicle identification numbers. In a final rule published on April 6, 2004, the Federal Motor Vehicle Theft Prevention Standard was extended to include all passenger cars and multipurpose passenger vehicles with a gross vehicle weight rating of 6,000 pounds or less, and to light duty trucks with major parts that are interchangeable with a majority of the covered major parts of multipurpose passenger vehicles. Each major component part must be either labeled or affixed with the VIN and its replacement component part must be marked with the DOT symbol, the letter
(R)and the manufacturers' logo. The final rule became effective September 1, 2006. Due to expansion of the Federal Motor Vehicle Theft Prevention Standard (Part 541), all passenger cars, and multipurpose passenger vehicles with a gross vehicle weight rating of 6,000 pounds or less, and to light duty trucks with major parts that are interchangeable with a majority of the covered major parts of multipurpose passenger vehicles, are required them to be parts marked. This creates a program change for this collection. Part 541 shows an increase in recordkeeping costs because there will be a greater number of vehicles required to be parts marked resulting in an additional cost of affixing labels or stamping the VIN on motor vehicles and startup costs for the manufacturers. NHTSA estimates the vehicle manufacturers will incur a total cost burden of $87,550,100 million. NHTSA estimates a decrease in reporting and recordkeeping hours because there is a more accurate count of the number of vehicles in compliance with the FMVTPS. However, there is an increase in the number of target area submissions required by the vehicle manufacturers. NHTSA estimates the vehicle manufacturers will incur a net decrease for a total annual hour burden of 502,519. *Estimated Annual Burden:* The overall total estimated annual hour burden for this collection is 925,852. The overall total estimated cost burden for this collection is $87,553,500 million. *Number of Respondents:* The total number of respondents for this collection (Part 541, 565 and Part 567) is 4,000. Comments are invited on: Whether the proposed collection of information is necessary for the proper performance of the functions of the Department, including whether the information will have practical utility; the accuracy of the Department's estimate of the burden of the proposed information collection; ways to enhance the quality, utility and clarity of the information to be collected; and ways to minimize the burden of the collection of information on respondents, including the use of automated collection techniques or other forms of information technology. Issued on: December 20, 2007. Julie Abraham, Director, International Policy Fuel Economy and Consumer Programs. [FR Doc. E7-25209 Filed 12-27-07; 8:45 am] BILLING CODE 4910-59-P DEPARTMENT OF TRANSPORTATION National Highway Traffic Safety Administration [Docket Number NHTSA-2007-0055] Reports, Forms, and Recordkeeping Requirements AGENCY: National Highway Traffic Safety Administration (NHTSA), Department of Transportation. ACTION: Request for public comment on proposed collection of information. SUMMARY: Before a Federal agency can collect certain information from the public, it must receive approval from the Office of Management and Budget (OMB). Under procedures established by the Paperwork Reduction Act of 1995, before seeking OMB approval, Federal agencies must solicit public comment on proposed collections of information, including extensions and reinstatement of previously approved collections. This document describes one collection of information for which NHTSA intends to seek OMB approval. DATES: Comments must be received on or before February 26, 2008. FOR FURTHER INFORMATION CONTACT: Mr. David Sparks, Office of Odometer Fraud Investigation, 1200 New Jersey Avenue, SE., Room W55-318, Washington, D.C. 20590-0001. Telephone:
(202)366-5953 SUPPLEMENTARY INFORMATION: Under the Paperwork Reduction Act of 1995, before an agency submits a proposed collection of information to OMB for approval, it must first publish a document in the **Federal Register** providing a 60-day comment period and otherwise consult with members of the public and affected agencies concerning each proposed collection of information. The OMB has promulgated regulations describing what must be included in such a document. Under OMB's regulation (at 5 CFR 1320.8(d)), an agency must ask for public comment on the following:
(i)Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;
(ii)The accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;
(iii)How to enhance the quality, utility, and clarity of the information to be collected;
(iv)How to minimize the burden of the collection of information on those who are to respond, including the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology (e.g. permitting electronic submission of responses). In compliance with these requirements, NHTSA asks for public comments on the following proposed collection of information: *Title:* 49 CFR Part 580 Odometer Disclosure Statement. *OMB Number:* 2127—0047. *Affected Public:* Households, Business, other for-profit and not-for-profit institutions, Federal Government, and State, Local, or Tribal Government. *Abstract:* The Federal Odometer Law, 49 U.S.C. Chapter 327, and implementing regulations, 49 CFR Part 580 require each transferor of a motor vehicle to provide the transferee with a written disclosure of the vehicle's mileage. This disclosure is to be made on the vehicle's title, or in the case of a vehicle that has never been titled, on a separate form. If the title is lost or is held by a lien holder, and where permitted by state law, the disclosure can be made on a state-issued, secure power of attorney. *Estimated Annual Burden:* 2,034,910. *Estimated Number of Respondents:* 162,808,900. *Comments are invited on:* whether the proposed collection of information is necessary for the proper performance of the functions of the Department, including whether the information will have practical utility; the accuracy of the Department's estimate of the burden of the proposed information collection; ways to enhance the quality, utility and clarity of the information to be collected; and ways to minimize the burden of the collection of information on respondents, including the use of automated collection techniques or other forms of information technology. Comments should refer to the docket and notice numbers above and be submitted by any of the following methods: • *Federal eRulemaking Portal: http://www.regulations.gov.* Follow the online instructions for submitting comments. • *DOT Internet site: http://dms.dot.gov* Follow the instructions for submitting comments. • *Mail:* Docket Management Facility, U.S. Department of Transportation, 1200 New Jersey Avenue, SE., West Building Ground Floor, Room W12-140, Washington, DC 20590-0001 • *Hand Delivery or Courier:* U.S. DOT, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC 20590-0001 between 9 a.m. and 5 p.m. EST, Monday through Friday, except Federal holidays. • *Fax:* 202-493-2251 *Instructions:* Comments must be written in the English language, and be no greater than 15 pages in length, although there is no limit to the length of necessary attachments to the comments. If comments are submitted in hard copy form, please ensure that two copies are provided. To receive confirmation that your comments were received, enclose a stamped, self-addressed postcard with the comments. Note that all comments received will be posted without change to *http://www.regulations.gov,* including any personal information provided. Please see the Privacy Act heading below. *Privacy Act:* Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT's complete Privacy Act Statement in the **Federal Register** published on April 11, 2000 (65 FR 19477-78) or you may visit *http://DocketInfo.dot.gov.* *To Read Comments submitted to the Docket:* visit the Docket Management System at the address and times given above. To read the comments on the Internet, take the following steps:
(1)Go to the Federal Docket Management System
(FDMS)Web page “ *http://www.regulations.gov* ”
(2)At that site, click on “search for dockets.”
(3)Select ( *http://www.regulations.gov/fdmspublic/component/main* )
(4)From the drop-down menu in the Agency field, select “National Highway Traffic Safety Administration”
(4)Enter number “2127-0047” (the Docket ID).
(5)Click on “submit.”
(6)The response should contain the docket summary information for this docket.
(7)Click on the comments you wish to see.
(8)You may download the comments. These files are imaged documents (i.e. Adobe Acrobat pdf files) and can be “word searched” using a suitable software application. Please note that it is recommended to search the Docket periodically, as new material is added as it becomes available. Issued on: December 20, 2007. Daniel C. Smith, Associate Administrator for Enforcement. [FR Doc. E7-25210 Filed 12-27-07; 8:45 am] BILLING CODE 4910-59-P DEPARTMENT OF TRANSPORTATION National Highway Traffic Safety Administration Denial of Motor Vehicle Defect Petition AGENCY: National Highway Traffic Safety Administration, (NHTSA), Department of Transportation. ACTION: Denial of a petition for a defect investigation. SUMMARY: This notice sets forth the reasons for the denial of a petition (Defect Petition DP06-005) submitted by Public Citizen to NHTSA's Office of Defects Investigation
(ODI)pursuant to 49 U.S.C. 30162, requesting that the agency commence a proceeding to determine the existence of a defect related to motor vehicle safety with regard to engine stalling in Model Year
(MY)2003-2005 Ford Taurus/Mercury Sable Flex Fuel Vehicles that operate using E85, an alternative fuel. After reviewing all available information, NHTSA has concluded that further expenditure of the agency's investigative resources on the issue raised by the petition is not warranted. The agency accordingly has denied the petition. FOR FURTHER INFORMATION CONTACT: Mr. Ajit Alkondon, Safety Defects Engineer, Defects Assessment Division, Office of Defects Investigation, NHTSA, 1200 New Jersey Avenue, SE., Washington DC 20590. Telephone 202-366-3565. SUPPLEMENTARY INFORMATION: On October 11, 2006, Public Citizen sent a letter to NHTSA regarding MY 2003-2005 Ford Taurus and Mercury Sable Flex Fuel Vehicles (FFV). The Ford Motor Company
(Ford)produced 228,000 of these vehicles in those model years. In the letter, Public Citizen petitioned NHTSA to investigate and determine whether the alleged stalling of these vehicles while operating on E85 constitutes a safety defect under the vehicle safety laws (49 U.S.C. Chapter 301). E85, an “alternative fuel” within the meaning of 49 U.S.C. 32901(a)(1)(D), is an alcohol/fuel mixture consisting of 85% denatured ethanol and 15% gasoline or diesel fuel. Flex fuel vehicles (FFVs, also known as “dual fueled automobiles”) are vehicles “capable of operating on alternative fuel and on gasoline or diesel fuel.” 49 U.S.C. 32901(a)(8)(A). An FFV is identical to its non-FFV counterpart, except that, because of the corrosive nature of the alternative fuel (in this case, the ethyl alcohol in E85), exposed metallic and rubber surfaces within the FFV fuel system have been replaced with materials more capable of resisting the corrosive effects of the alternative fuel to prevent excessive wear of these surfaces from exposure to E85. Public Citizen's Petition In addition to seeking a defect investigation, the petition also asks NHTSA to reclaim credits claimed by Ford for these vehicles due to their dual fuel status under the Corporate Average Fuel Economy
(CAFE)program. See 49 U.S.C. 32905-32906. Although that issue is not addressed in this notice, the petition focuses primarily on this CAFE credit issue and the availability of E85. The great majority of the allegations in the petition concern difficulty in starting the vehicles and make no reference to safety issues. The petition mentions one instance in which, after the owner experienced difficulty starting the vehicle and drove the car out of his garage, the vehicle “began to stall.” The petition does not allege any crashes, injuries, or (with the possible exception of the one alleged stalling incident), any unsafe events involving these vehicles. NHTSA's Review of the Allegations Made in the Petition With little to go on based on the petition itself, ODI looked at various sources of information to determine whether or not there was any basis for a safety investigation of these vehicles with regard to alleged engine stalling. ODI reviewed complaints submitted by owners of these vehicles to NHTSA and to Ford (including a complaint concerning the one instance of possible stalling cited in the petition), the experience of state-owned fleets of these vehicles, Early Warning Reporting
(EWR)data, actions taken by Ford, and certain information submitted by Ford. In any investigation involving allegations of stalling, ODI examines a number of factors, including: The rate at which stalling occurs in the whole population of subject vehicles (often expressed as the number of vehicles that have experienced the phenomenon per hundred thousand), the speeds at which stalling occurs, the type of operation during which stalling occurs ( *e.g.* , when starting, accelerating, decelerating, or cruising), whether the vehicle can quickly be restarted after stalling, whether the stalling affects steering functions, whether the stalling affects braking functions, and any crashes or other unsafe events that may have resulted from the stalling. In deciding whether or not alleged stalling merits a full investigation, ODI also considers those criteria. Ford's Actions Concerning These Vehicles In response to customer complaints about the operation of these vehicles, Ford released two Technical Service Bulletins (TSBs): TSB 05-11-13 and TSB 06-05-05. TSB 05-11-13, issued on June 13, 2005, pertains to both FFV and non-FFV Ford Taurus/Mercury Sable vehicles for MY 2004 and 2005. The TSB addresses the following issues: lack of power at highway speeds, RPM dip after cold start, malfunction indicator lamp
(MIL)on with diagnostic trouble code
(DTC)P0316, intermediate clutch failure due to low transmission oil pressure, misfire at low load/low RPM, or load surge at low speeds, hard start and rough idle, and inaccurate display of fuel economy in message center. Ford explained that TSB 05-11-13 was created to address specific drivability symptoms associated with the 3.0L engine in MY 2004 through 2005 model Taurus/Sable vehicles, independent of the type of fuel used. The repair procedure for this TSB includes reprogramming the Powertrain Control Module
(PCM)with updated software. TSB 06-05-05, published on March, 20, 2006, pertains to Ford Taurus/Mercury Sable FFVs for MY 2004-2006. This TSB addresses a long crank/hard start condition when the vehicles operate on E85 fuel. Similar to TSB 05-11-13, the repair procedure for this TSB requires reprogramming the PCM with an updated software release. While the letter from Public Citizen concerns subject vehicles in MY 2003 through 2005, the two TSBs issued by Ford cover MY 2004 through 2005 and 2004 through 2006, respectively. Ford explained that the model years 2001 through 2003 Taurus/Sable vehicles have a different PCM than the MY 2004 through 2006 Taurus/Sable vehicles. Further, the issues brought up in the Public Citizen letter—long crank/hard start and low speed stalls—are predominantly confined to the 2004 to 2006 model year vehicles. As stated above, Ford issued TSB 06-05-05 to address the long crank/hard start problems associated with MY 2004 through 2006 Ford Taurus/Mercury Sable vehicles. Ford also initiated Extended Coverage Program
(ECP)06N07 to address this condition. Ford did not extend ECP 06N07 to MY 2003 vehicles since these vehicles have a different PCM and are covered under a separate ECP. A search of Ford's Analytical Warranty System database revealed that of the 649 vehicles receiving the TSB 06-05-05 repair, only 12, or 1.8%, of the vehicles required service for similar issues after the repair. Of these 12, only one vehicle complained of a stall while driving. (As explained below, this stall was apparently not related to use of E85.) This suggests a high TSB effectiveness. The Complaint Cited in the Petition ODI interviewed the complainant named in the Public Citizen letter and inquired concerning his experiences with the subject vehicle and its performance when operated on either gasoline or E85. The consumer stated that he had purchased a new 2005 Ford Taurus FFV and that, when operating the vehicle on gasoline alone, he had experienced no driving problems. However, when the consumer operated the vehicle on E85, he experienced hard starting and low speed stalls while the engine was cold. The consumer had the adjustments called for by TSB 05-11-13 performed on his vehicle three times, but the problems persisted. He then sold the vehicle back to the Ford dealership after driving only 980 miles. TSB 06-05-05 was never performed on the vehicle. Other Complaints In addition to the vehicle owned by the complainant discussed above, ODI confirmed only three other vehicles that had experienced instances of stalling from a population of 228,000 vehicles. One, a 2004 Ford Taurus FFV, was the subject of a Vehicle Owner Questionnaire
(VOQ)submitted to NHTSA. ODI contacted this consumer and learned that the consumer's main concern was difficulty starting the vehicle. The consumer stated that he brought the vehicle into a repair shop for service and had TSB 06-05-05 performed on his vehicle. Eventually, the work Ford did on the car reduced the hard starting problem and apparently eliminated the stalling problem. The second vehicle that experienced stalling, a 2005 Ford Taurus FFV, was the subject of a complaint received by Ford and recorded in its complaint database. ODI has contacted this consumer and learned that the consumer experienced both engine stalling and hard starting problems. The consumer did not have TSB06-05-05 performed on his vehicle, and sold the vehicle shortly after his vehicle exhibited these symptoms. The third vehicle that experienced stalling, a 2004 Ford Taurus FFV, was the vehicle returned for repair after application of TSB 06-05-05, mentioned above. This particular complaint suggested a single stalling event while driving, after which the vehicle restarted with no additional problems. Ultimately, this vehicle was repaired by performing technical service unrelated to the repair methods for engine stalling due to E85 usage. Therefore, the stalling problem was apparently unrelated to E-85 usage, and this vehicle is not considered as one that experienced E85-related stalling. In total, ODI was able to confirm that just three FFV vehicles (one 2004 Taurus and two 2005 Tauruses) experienced stalls related to E85 operation. ODI was not able to confirm any stalls in the population of 2003 Ford Taurus/Mercury vehicles. Fleet Experience To assess E85 performance in vehicles most likely to use it frequently, ODI obtained a list of fleets operating the subject vehicles. ODI contacted six of the fleets-the State of Minnesota; the Iowa, Illinois, Nebraska, and Wisconsin Departments of Transportation; and the Minnesota Department of Natural Resources. In total, these fleets operate approximately 500 of the subject vehicles. Five out of the six fleets reported incidents of long crank/hard start in the subject vehicles. However, none of the six fleets reported stalling issues. Fleet customers report that they have taken advantage of the TSBs issued by Ford that address this long crank/hard start issue, and that there have been significant improvements in the subject vehicle performance while using E85 subsequent to the repairs. Conclusions Nearly all of the allegations concerning the operation of these vehicles involve long crank/hard starting, not stalling. Based on ODI's inquiry, only three of the subject vehicles (out of a population of 228,000 vehicles) have experienced engine stalling in connection with their operation using E85. This indicates a very low rate of stalling that is nearly identical to the rate of stalling in non-FFV Taurus and Sable vehicles and very low when compared to the rates experienced by non-FFV that ODI has reviewed. The stalling that has occurred has apparently not resulted in any crashes, loss of steering or braking control, or high risk events. The stalling seems to occur either at start-up or at low speeds. Moreover, at least with regard to the one vehicle that experienced stalling apparently related to E85 use and later received the repair procedure called for by Ford's TSB 06-05-05, this procedure seemed to cure the problem. Due to the very low incidence of vehicle stalling resulting from the use of E85 within the subject vehicles and the extremely low likelihood of an unsafe occurrence arising from the type of stalls that have occurred, it is unlikely that NHTSA would issue an order for the notification and remedy of a safety defect in this matter. NHTSA notes that the issues consumers primarily complain of—namely long crank/hard start and stall while driving—are adequately addressed by the TSBs issued by Ford in response to consumer complaints. Because we believe the petition does not provide a technical basis on which to proceed, and in view of the need to allocate NHTSA's limited resources so as to accomplish the agency's safety priorities, the petition is denied. This action does not constitute a finding by NHTSA that a safety-related defect does not exist. The agency will take further action if warranted by future circumstances. Authority: 49 U.S.C. 30162(d); delegation of authority at CFR 1.50 and 501.8. Issued on: December 13, 2007. Daniel C. Smith, Associate Administrator for Enforcement. [FR Doc. E7-25096 Filed 12-27-07; 8:45 am] BILLING CODE 4910-59-P DEPARTMENT OF TRANSPORTATION Pipeline and Hazardous Materials Safety Administration [Docket ID PHMSA-97-2995] Pipeline Safety: Random Drug Testing Rate AGENCY: Pipeline and Hazardous Materials Safety Administration (PHMSA), DOT. ACTION: Notice of minimum annual percentage rate for random drug testing. SUMMARY: PHMSA has determined that the minimum random drug testing rate for covered employees will remain at 25 percent during calendar year 2008. DATES: Effective January 1, 2008, through December 31, 2008. FOR FURTHER INFORMATION CONTACT: Stanley Kastanas, Director, Drug and Alcohol Policy and Investigations, PHMSA, U.S. Department of Transportation, telephone
(202)550-0629 or e-mail *Stanley.kastanas@dot.gov.* SUPPLEMENTARY INFORMATION: Operators of gas, hazardous liquid, and carbon dioxide pipelines and operators of liquefied natural gas facilities must select and test a percentage of covered employees for random drug testing. Pursuant to 49 CFR 199.105(c)(2), (3), and (4), the PHMSA Administrator's decision on whether to change the minimum annual random drug testing rate is based on the reported random drug test positive rate for the pipeline industry. The data considered by the Administrator comes from operators' annual submissions of Management Information System
(MIS)reports required by 49 CFR199.119(a). If the reported random drug test positive rate is less than one percent, the Administrator may continue the minimum random drug testing rate at 25 percent. In 2006, the random drug test positive rate was less than one percent. Therefore, the minimum random drug testing rate will remain at 25 percent for calendar year 2008. In reference to the notice published in 70 FR 20800, PHMSA intends to publish an Advisory Bulletin specifying the methodology for reporting calendar year 2007 MIS contractor data to PHMSA. Therefore, operators must ensure records on contract employees continue to be maintained in calendar year 2008. Authority: 49 U.S.C. 5103, 60102, 60104, 60108, 60117, and 60118; 49 CFR 1.53. Issued in Washington, DC on December 19, 2007. Jeffrey D. Wiese, Associate Administrator for Pipeline Safety. [FR Doc. E7-25136 Filed 12-27-07; 8:45 am] BILLING CODE 4920-60-P DEPARTMENT OF TRANSPORTATION Surface Transportation Board Release of Waybill Data The Surface Transportation Board has received a request from GATX Rail (WB512-13—10/4/07), for permission to use certain data from the Board's Carload Waybill Samples. A copy of this request may be obtained from the Office of Economics, Environmental Analysis, and Administration. The waybill sample contains confidential railroad and shipper data; therefore, if any parties object to these requests, they should file their objections with the Director of the Board's Office of Economics, Environmental Analysis, and Administration within 14 calendar days of the date of this notice. The rules for release of waybill data are codified at 49 CFR 1244.9. Contact: Mac Frampton,
(202)245-0317. Vernon A. Williams, Secretary. [FR Doc. E7-25152 Filed 12-27-07; 8:45 am] BILLING CODE 4915-01-P DEPARTMENT OF TRANSPORTATION Surface Transportation Board Release of Waybill Data The Surface Transportation Board has received a request from the Association of American Railroads (WB463-10—9/13/07) for permission to use certain data from the Board's Carload Waybill Samples. A copy of this request may be obtained from the Office of Economics, Environmental Analysis, and Administration. The waybill sample contains confidential railroad and shipper data; therefore, if any parties object to these requests, they should file their objections with the Director of the Board's Office of Economics, Environmental Analysis, and Administration within 14 calendar days of the date of this notice. The rules for release of waybill data are codified at 49 CFR 1244.9. Contact: Mac Frampton,
(202)245-0317. Vernon A. Williams, Secretary. [FR Doc. E7-25154 Filed 12-27-07; 8:45 am] BILLING CODE 4915-01-P DEPARTMENT OF TRANSPORTATION Surface Transportation Board Release of Waybill Data The Surface Transportation Board has received a request from Mayer Brown on behalf of The BNSF Railway Company
(BNSF)(WB461-14—9/20/07) for permission to use certain data from the Board's Carload Waybill Samples. A copy of this request may be obtained from the Office of Economics, Environmental Analysis, and Administration. The waybill sample contains confidential railroad and shipper data; therefore, if any parties object to these requests, they should file their objections with the Director of the Board's Office of Economics, Environmental Analysis, and Administration within 14 calendar days of the date of this notice. The rules for release of waybill data are codified at 49 CFR 1244.9. Contact: Mac Frampton,
(202)245-0317. Vernon A. Williams, Secretary. [FR Doc. E7-25155 Filed 12-27-07; 8:45 am] BILLING CODE 4915-01-P DEPARTMENT OF TRANSPORTATION Surface Transportation Board Release of Waybill Data The Surface Transportation Board has received a request from Michael Behe representing FRN, LLC (WB604-5—8/20/07) for permission to use certain data from the Board's 2006 Carload Waybill Sample. A copy of this request may be obtained from the Office of Economics, Environmental Analysis, and Administration. The waybill sample contains confidential railroad and shipper data; therefore, if any parties object to these requests, they should file their objections with the Director of the Board's Office of Economics, Environmental Analysis, and Administration within 14 calendar days of the date of this notice. The rules for release of waybill data are codified at 49 CFR 1244.9. Contact: Mac Frampton,
(202)245-0317. Vernon A. Williams, Secretary. [FR Doc. E7-25159 Filed 12-27-07; 8:45 am] BILLING CODE 4915-01-P DEPARTMENT OF TRANSPORTATION Surface Transportation Board Release of Waybill Data The Surface Transportation Board has received a request from Saul Ewing on behalf of Trinity Industries, Inc. (WB605-3—8/8/07) for permission to use certain data from the Board's Carload Waybill Samples. A copy of the requests may be obtained from the Office of Economics, Environmental Analysis, and Administration. The waybill sample contains confidential railroad and shipper data; therefore, if any parties object to these requests, they should file their objections with the Director of the Board's Office of Economics, Environmental Analysis, and Administration within 14 calendar days of the date of this notice. The rules for release of waybill data are codified at 49 CFR 1244.9. Contact: Mac Frampton,
(202)245-0317. Vernon A. Williams, Secretary. [FR Doc. E7-25160 Filed 12-27-07; 8:45 am] BILLING CODE 4915-01-P DEPARTMENT OF TRANSPORTATION Surface Transportation Board Release of Waybill Data The Surface Transportation Board has received a request from Mitsui Rail Capital (WB992-1—10/15/07), for permission to use certain data from the Board's Carload Waybill Samples. A copy of this request may be obtained from the Office of Economics, Environmental Analysis, and Administration. The waybill sample contains confidential railroad and shipper data; therefore, if any parties object to these requests, they should file their objections with the Director of the Board's Office of Economics, Environmental Analysis, and Administration within 14 calendar days of the date of this notice. The rules for release of waybill data are codified at 49 CFR 1244.9. Contact: Mac Frampton,
(202)245-0317. Vernon A. Williams, Secretary. [FR Doc. E7-25161 Filed 12-27-07; 8:45 am] BILLING CODE 4915-01-P DEPARTMENT OF THE TREASURY Community Development Financial Institutions Fund Funding Opportunity Title: Notice of Allocation Availability
(NOAA)Inviting Applications for the CY 2008 Allocation Round of the New Markets Tax Credit Program *Announcement Type:* Initial announcement of tax credit allocation availability. DATES: Electronic applications must be received by 5 p.m. ET on March 5, 2008. Applications sent by mail, facsimile or other form will not be accepted. The Community Development Financial Institutions Fund (the Fund) will not accept applications in paper form, other than the assigned signature page and certain paper attachments (see section IV.D. of this NOAA for more details). Applications must meet all eligibility and other requirements and deadlines, as applicable, set forth in this NOAA. Allocation applicants that are not yet certified as Community Development Entities
(CDEs)must submit an application for certification as a CDE that is postmarked on or before February 6, 2008 (see section III of this NOAA for more details). *Executive Summary:* This NOAA is issued in connection with the calendar year 2008 tax credit allocation round of the New Markets Tax Credit
(NMTC)Program, as authorized by Title I, subtitle C, section 121 of the Community Renewal Tax Relief Act of 2000 (Pub. L. 106-554) and amended by section 221 of the American Jobs Creation Act of 2004 (Pub. L. 108-357), section 101 of the Gulf Opportunity Zone Act of 2005 (Pub. L. 108-357), and Division A, section 102 of the Tax Relief and Health Care Act of 2006 (Pub. L. 109-432) (the Act). Through the NMTC Program, the Fund provides authority to CDEs to offer an incentive to investors in the form of tax credits over seven years, which is expected to stimulate the provision of private investment capital that, in turn, will facilitate economic and community development in Low-Income Communities. Through this NOAA, the Fund announces the availability of $3.5 billion of NMTC authority authorized by the Act. In this NOAA, the Fund addresses specifically how an entity may apply to receive an allocation of NMTCs, the competitive procedure through which NMTC Allocations will be made, and the actions that will be taken to ensure that proper allocations are made to appropriate entities. I. Allocation Availability Description A. Programmatic Changes 1. *Non-Metropolitan Counties* . As provided by section 102(b)of the Act, the Fund shall ensure that non-metropolitan counties receive a proportional allocation of Qualified Equity Investments
(QEIs)under the NMTC Program. To guide the Fund in implementing this requirement, on May 22, 2007, the Fund published in the **Federal Register** a Request for Public Comments (72 FR 28766). Commentators were asked to consider a number of issues:
(a)What outcome should be achieved? Commentators were asked to consider, for example, whether a proportionate allocation of QEIs should be provided:
(i)To investors that reside in non-metropolitan counties;
(ii)to Allocatees that are headquartered in non-metropolitan counties;
(iii)to Allocatees that principally serve non-metropolitan counties; or
(iv)to finance Qualifying Low Income Community Investments (QLICIs) in non-metropolitan counties.
(b)How to measure “proportionality”? Should proportionality be based upon, for example:
(i)The total proportion of the U.S. population residing in non-metropolitan counties;
(ii)the total proportion of NMTC-eligible census tracts that are located in non-metropolitan areas; or
(iii)the total proportion of applicants in a given round that are principally serving, and/or headquartered in, non-metropolitan counties? Also, to the extent that proportionality is based upon QLICIs, should the Fund consider the total number of QLICIs made, or the total dollar amount of those QLICIs?
(c)Should the Fund implement changes to its application review process to achieve desired outcomes, including providing a new set of priority points and/or re-ranking certain applicants?
(d)What compliance mechanisms are needed to ensure that desired outcomes are achieved? Commentators were nearly unanimous in the opinion that:
(i)The Fund should focus its efforts on ensuring that a proportional allocation of QLICIs are made in non-metropolitan areas, and that the location of the investor is not pertinent;
(ii)the proportionality test should be based upon the total dollar amount of QLICIs made, rather than the total number of QLICIs made; and
(iii)applicants should be required to specify the percentage of investments they intend to make in non-metropolitan areas, and then be held to achieving this benchmark through their Allocation Agreements. The Fund has adopted all three of these positions. Commentators were divided with respect to the appropriate benchmark for ensuring a proportional allocation of QLICIs in non-metropolitan areas. Some suggested 17.4 percent, which is the proportion of the U.S. population living in non-metropolitan counties according to the Department of Agriculture's “Beale Codes.” Some commentators suggested 21 percent, which is the proportion of the U.S. population living in non-metropolitan counties according to the Department of Agriculture's Economic Research Service. Some commentators suggested 25 percent, which is the percentage of NMTC eligible low-income census tracts located in non-metropolitan counties. Some commentators suggested 35 percent, as a means to make up for perceived “under-funding” in prior NMTC Program allocation rounds. The Fund has selected 20 percent as the appropriate benchmark for ensuring a proportional allocation of QLICIs in non-metropolitan areas, which approximates the percentage of the U.S. population that Fund data indicates resides in non-metropolitan counties. To correct information stated in the Request for Comments, the Fund currently relies upon the 1999 OMB definition of Non-Metropolitan counties [OMB Bulletin 99-04], applied to the 2000 Census data, to determine NMTC Program eligibility. This data is publicly available through the Fund's Mapping System (CIMS). According to this data, 19.6 percent of the U.S. population resides in non-metropolitan counties. The Fund believes that it is in the best interest of the Fund, the Internal Revenue Service
(IRS)and NMTC Program users to set its benchmark based on this data, since this is the data that currently feeds into Fund's compliance and monitoring systems, as well as the data that NMTC Program users can readily access to determine which counties qualify as non-metropolitan counties. Commentators generally did not suggest that any special preference or consideration should be given to a CDE solely because it is headquartered in a non-metropolitan area. The Fund concurs with this position. Commentators were generally of the opinion that the Fund should give special consideration (most notably, priority points) to CDEs that demonstrate a track record of principally serving non-metropolitan areas, and/or those that make a significant forward-looking commitment to serving non-metropolitan areas. In addition, commentators generally did not object to re-ranking lower scoring applicants, if necessary to ensure that the proportional allocation is achieved. While the Fund does not concur that priority points are the preferred solution (since priority points alone may not guarantee the desired outcome), the Fund has determined that special consideration should be given to “Rural CDEs”—those applicants that over the past five years have dedicated at least 50 percent of their activities to Non-Metropolitan counties and have committed that at least 50 percent of their NMTC activities will be conducted in such areas should they receive an allocation award. The Fund will ensure that the percentage of allocatees that are Rural CDEs is not less than the percentage of applicants deemed eligible for Phase 2 of the review process that are Rural CDEs. With respect to compliance, commentators generally agreed that Allocatees should be held to their application commitments to invest in non-metropolitan counties as a condition of their Allocation Agreements. The Fund concurs. The Fund will ask each applicant to indicate both a minimum and maximum percentage of its requested allocation that it would commit to deploying in non-metropolitan counties. Applicants will be held to a designated percentage (no less than the stated minimum and no greater than the stated maximum) through their Allocation Agreements. In summary, and as further discussed in section V.C. of this document, the Fund will ensure that the proportion of allocatees that are Rural CDEs is, at a minimum, equal to the proportion of applicants in the Phase 2 review pool that are Rural CDEs; and ensure that at least 20 percent of the QLICIs made using QEI proceeds are invested in Non-Metropolitan counties. 2. *Allocation Amounts* . As described in section IIA, the Fund anticipates that it will not provide an allocation award of more than $125 million per applicant. This limitation was set at $150 million last year, but was reduced this year due, in part, to the lower allocation authority available for distribution in this round. B. *Program guidance and regulations* : This NOAA provides guidance for the application and allocation of NMTCs for the sixth round of the NMTC Program and should be read in conjunction with:
(i)Guidance published by the Fund on how an entity may apply to become certified as a CDE (66 FR 65806, December 20, 2001);
(ii)the final regulations issued by the Internal Revenue Service (26 CFR 1.45D-1, published on December 28, 2004) and related guidance, notices and other publications; and
(iii)the application and related materials for this sixth NMTC Program allocation round. All such materials may be found on the Fund's Web site at *http://www.cdfifund.gov* . The Fund encourages applicants to review these documents. Capitalized terms used but not defined in this NOAA shall have the respective meanings assigned to them in the allocation application, IRC 45D or the IRS regulations. II. Allocation Information A. *Allocation amounts:* Pursuant to the Act, the Fund expects that it may allocate to CDEs the authority to issue to their investors up to the aggregate amount of $3.5 billion in equity as to which NMTCs may be claimed, as permitted under IRC 45D(f)(1)(D). The Fund anticipates that, under this NOAA, it will not issue more than $125 million in tax credit allocation authority per applicant. The Fund, in its sole discretion, reserves the right to allocate amounts in excess of or less than the anticipated maximum allocation amount if the Fund deems it appropriate. In order to receive an allocation in excess of the $125 million cap, an applicant will likely need to demonstrate, for example, that:
(i)No part of its strategy can be successfully implemented without an allocation in excess of the applicable cap; or
(ii)its strategy will produce extraordinary community impact. The Fund reserves the right to allocate tax credit authority to any, all or none of the entities that submit an application in response to this NOAA, and in any amount it deems appropriate. B. *Types of awards:* NMTC Program awards are made in the form of tax credit authority. C. *Notice of Allocation and Allocation Agreement:* Each Allocatee under this NOAA must sign a Notice of Allocation and an Allocation Agreement before the NMTC Allocation is effective. The Notice of Allocation and the Allocation Agreement contain the terms and conditions of the allocation. For further information, see section VI of this NOAA. III. Eligibility A. *Eligible applicants:* IRC 45D specifies certain eligibility requirements that each applicant must meet to be eligible to apply for an allocation of NMTCs. The following sets forth additional detail and certain additional dates that relate to the submission of applications under this NOAA for the $3.5 billion in general NMTC allocation authority. 1. *CDE certification:* For purposes of this NOAA, the Fund will not consider an application for an allocation of NMTCs unless:
(a)The applicant is certified as a CDE at the time the Fund receives its NMTC Program allocation application; or
(b)the applicant submits an application for certification as a CDE that is postmarked on or before February 6, 2008. Applicants for certification may obtain a CDE certification application through the Fund's Web site at *http://www.cdfifund.gov* . Applications for CDE certification must be submitted as instructed in the application form. An applicant that is a community development financial institution
(CDFI)or a specialized small business investment company (SSBIC) does not need to submit a CDE certification application, but must register as a CDE on the Fund's website on or before 5 p.m. ET on February 6, 2008. The Fund will not provide allocations of NMTCs to applicants that are not certified as CDEs. See section IV.D.1.(c) of this NOAA for further requirements relating to postmarks. If an applicant that has already been certified as a CDE wishes to change its designated CDE service area, it must submit its request for such a change to the Fund; and said request must be received by the Fund by 5 p.m. ET on March 5, 2008. The CDE service area change request must be sent from the applicant's authorized representative and include the applicable CDE control number, the revised service area designation, and an updated accountability chart that reflects representation from Low-Income Communities in the revised service area. The service area change request must be sent by e-mail to *cdfihelp@cdfi.treas.gov* or by facsimile to
(202)622-7754. 2. *Prior awardees or Allocatees:* Applicants must be aware that success in a prior round of any of the Fund's programs is not indicative of success under this NOAA. Prior awardees of any component of the Fund's Community Development Financial Institutions
(CDFI)Program, Bank Enterprise Award
(BEA)Program, the Native Initiatives, or any other Fund program and prior Allocatees under the NMTC Program are eligible to apply under this NOAA, except as follows:
(a)*Prior Allocatees and Qualified Equity Investment
(QEI)issuance requirements* : The following describes the QEI issuance requirements applicable to prior Allocatees, including those Allocatees that received allocations pursuant to special allocation authority under the Gulf Opportunity Zone Act of 2005 (“GO Zone Allocatees”). A prior Allocatee in the first round of the NMTC Program (CY 2001-2002) is not eligible to receive a NMTC Allocation pursuant to this NOAA unless the Allocatee can demonstrate that, as of 11:59 p.m. ET on June 13, 2008, it has:
(i)Issued and received funds in-hand (the term “funds in-hand” does not include committed funding) from its investors for 100 percent of its QEIs relating to its CY 2001-2002 NMTC Allocation; or
(ii)issued and received funds in-hand from its investors for at least 75 percent of its QEIs and that 100 percent of its total CY 2001-2002 Allocation has been exchanged for funds in-hand from, or has been committed by, its investors. A prior Allocatee in the second round of the NMTC Program (CY 2003-2004) is not eligible to receive a NMTC Allocation pursuant to this NOAA unless the Allocatee can demonstrate that, as of 11:59 p.m. ET on June 13, 2008, it has:
(i)Issued and received funds in-hand from its investors for at least 80 percent of its QEIs relating to its CY 2003-2004 NMTC Allocation; or
(ii)issued and received funds in-hand from its investors for at least 60 percent of its QEIs and that 100 percent of its total CY 2003-2004 NMTC Allocation has been exchanged for funds in-hand from, or has been committed by, its investors. A prior Allocatee in the third round of the NMTC Program (CY 2005) is not eligible to receive a NMTC Allocation pursuant to this NOAA unless the Allocatee can demonstrate that, as of 11:59 p.m. ET on June 13, 2008, it has:
(i)Issued and received funds in-hand from its investors for at least 60 percent of its QEIs relating to its CY 2005 NMTC Allocation; or
(ii)issued and received funds in-hand from its investors for at least 50 percent of its QEIs and that at least 80 percent of its total CY 2005 NMTC Allocation has been exchanged for funds in-hand from, or has been committed by, its investors. A prior Allocatee (with the exception of a GO Zone Allocatee) in the fourth round of the NMTC Program (CY 2006) is not eligible to receive a NMTC Allocation pursuant to this NOAA unless the Allocatee can demonstrate that, as of 11:59 p.m. ET on June 13, 2008, it has:
(i)Issued and received funds in-hand from its investors for at least 50 percent of its QEIs relating to its CY 2006 NMTC Allocation; or
(ii)issued and received funds in-hand from its investors for at least 40 percent of its QEIs and that at least 80 percent of its total CY 2006 NMTC Allocation has been exchanged for funds in-hand from, or has been committed by, its investors. A prior GO Zone Allocatee in the fourth round is not eligible to receive a NMTC Allocation pursuant to this NOAA unless the Allocatee can demonstrate that, as of 11:59 p.m. ET on June 13, 2008, it has issued and received funds in-hand from its investors for at least 20 percent of its QEIs relating to its CY 2006 NMTC Allocation. A prior Allocatee (with the exception of a GO Zone Allocatee) in the fifth round of the NMTC Program (CY 2007) is not eligible to receive a NMTC Allocation pursuant to this NOAA unless the Allocatee can demonstrate that, as of 11:59 p.m. ET on June 13, 2008, it has:
(i)Issued and received funds in-hand from its investors for at least 50 percent of its QEIs relating to its CY 2006 NMTC Allocation; or
(ii)issued and received funds in-hand from its investors for at least 20 percent of its QEIs and that at least 60 percent of its total CY 2007 NMTC Allocation has been exchanged for funds in-hand from, or has been committed by, its investors. A prior GO Zone Allocatee in the fifth round is not required to meet the above QEI issuance and commitment thresholds with regard to the GO Zone NMTCs. Further, an entity is not eligible to receive a NMTC Allocation pursuant to this NOAA if another entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant (as determined by the Fund) is a prior Allocatee and has not met the requirements for the issuance and/or commitment of QEIs as set forth above for the Allocatees in the prior allocation rounds of the NMTC Program. Notwithstanding the above, if an applicant has received an allocation in multiple allocation rounds of the NMTC Program, the applicant shall be deemed to be eligible to apply for a NMTC Allocation pursuant to this NOAA if the applicant can demonstrate that, as of 11:59 p.m. ET on June 13, 2008, it has issued and received funds in-hand from its investors for at least 70 percent of its QEIs relating to its cumulative allocation amounts from prior NMTC Program rounds (CY 2001-2007), exclusive of:
(i)GO Zone allocations received by Allocatees under the CY 2007 allocation round; and
(ii)GO Zone allocations received by Allocatees under the CY 2006 round, provided that the Allocatee has issued and received funds in-hand from its investors for at least 20 percent of its QEIs relating to its CY 2006 GO Zone allocation. For purposes of this section of the NOAA, the Fund will only count as “issued” those QEIs that have been finalized in the Fund's Allocation Tracking System
(ATS)by the deadlines specified above. Allocatees and their Subsidiary transferees, if any, are advised to access ATS to record each QEI that they issue to an investor in exchange for funds in-hand. For purposes of this section of the NOAA, “committed” QEIs are only those Equity Investments that are evidenced by a written, signed document in which an investor:
(i)Commits to make an investment in the Allocatee in a specified amount and on specified terms;
(ii)has made an initial disbursement of the investment proceeds to the Allocatee, and such initial disbursement has been recorded in ATS as a QEI;
(iii)commits to disburse the remaining investment proceeds to the Allocatee based on specified amounts and payment dates; and
(iv)commits to make the final disbursement to the Allocatee no later than June 13, 2010. The applicant will be required, upon notification from the Fund, to submit adequate documentation to substantiate the required issuances of and commitments for QEIs. Prior Allocatees that require any action by the Fund ( *e.g.* , certifying a subsidiary entity as a CDE; adding a subsidiary CDE to an Allocation Agreement; etc.) in order to meet the QEI issuance requirements above must submit their requests by no later than March 28, 2008 in order to guarantee that the Fund completes all necessary approvals prior to June 13, 2008. Applicants for certification may obtain a CDE certification application through the Fund's Web site at *http://www.cdfifund.gov* . Applications for CDE certification must be submitted as instructed in the application form.
(b)*Failure to meet reporting requirements:* The Fund will not consider an application submitted by an applicant if the applicant, or an entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant (as determined by the Fund), is a prior Fund awardee or Allocatee under any Fund program and is not current on the reporting requirements set forth in a previously executed assistance, allocation or award agreement(s), as of the application deadline of this NOAA. Please note that the Fund only acknowledges the receipt of reports that are complete. As such, incomplete reports or reports that are deficient of required elements will not be recognized as having been received.
(c)*Pending resolution of noncompliance:* If an applicant is a prior awardee or Allocatee under any Fund program and if:
(i)It has submitted complete and timely reports to the Fund that demonstrate noncompliance with a previous assistance, award or Allocation Agreement; and
(ii)the Fund has yet to make a final determination as to whether the entity is in default of its previous assistance, award or Allocation Agreement, the Fund will consider the applicant's application under this NOAA pending full resolution, in the sole determination of the Fund, of the noncompliance. Further, if another entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant (as determined by the Fund), is a prior Fund awardee or Allocatee and if such entity:
(i)Has submitted complete and timely reports to the Fund that demonstrate noncompliance with a previous assistance, award or Allocation Agreement; and
(ii)the Fund has yet to make a final determination as to whether the entity is in default of its previous assistance, award or Allocation Agreement, the Fund will consider the applicant's application under this NOAA pending full resolution, in the sole determination of the Fund, of the noncompliance.
(d)*Default status:* The Fund will not consider an application submitted by an applicant that is a prior Fund awardee or Allocatee under any Fund program if, as of the application deadline of this NOAA, the Fund has made a final determination that such applicant is in default of a previously executed assistance, allocation or award agreement(s) and the Fund has provided written notification of such determination to such applicant. Further, an entity is not eligible to apply for an allocation pursuant to this NOAA if, as of the application deadline of this NOAA, the Fund has made a final determination that another entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant (as determined by the Fund):
(i)Is a prior Fund awardee or Allocatee under any Fund program;
(ii)has been determined by the Fund to be in default of a previously executed assistance, allocation or award agreement(s); and
(iii)has been provided written notification of such default determination by the Fund.
(e)*Termination in default:* The Fund will not consider an application submitted by an applicant that is a prior Fund awardee or Allocatee under any Fund program if:
(i)Within the 12-month period prior to the application deadline of this NOAA, the Fund has made a final determination that such applicant's prior award or allocation terminated in default of a previously executed assistance, allocation or award agreement(s);
(ii)the Fund has provided written notification of such determination to such applicant; and
(iii)the final reporting period end date for the applicable terminated assistance, allocation or award agreement(s) falls in such applicant's 2006 or 2007 fiscal year. Further, an entity is not eligible to apply for an allocation pursuant to this NOAA if:
(i)Within the 12-month period prior to the application deadline of this NOAA, the Fund has made a final determination that another entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant (as determined by the Fund), is a prior Fund awardee or Allocatee under any Fund program whose award or allocation terminated in default of a previously executed assistance, allocation or award agreement(s);
(ii)the Fund has provided written notification of such determination to the defaulting entity; and
(iii)the final reporting period end date for the applicable terminated assistance, allocation or award agreement(s) falls in the defaulting entity's 2006 or 2007 fiscal year.
(f)*Undisbursed award funds:* The Fund will not consider an application submitted by an Applicant that is a prior Fund Awardee under any Fund program if the Applicant has a balance of undisbursed award funds (defined below) under said prior award(s), as of the applicable application deadline of this NOAA. Further, an entity is not eligible to apply for an award pursuant to this NOAA if another entity that Controls the Applicant, is Controlled by the Applicant or shares common management officials with the Applicant (as determined by the Fund), is a prior Fund Awardee under any Fund program, and has a balance of undisbursed award funds under said prior award(s), as of the applicable application deadline of this NOAA. In a case where another entity that Controls the Applicant, is Controlled by the Applicant or shares common management officials with the Applicant (as determined by the Fund), is a prior Fund Awardee under any Fund program and has a balance of undisbursed award funds under said prior award(s) as of the applicable application deadline of this NOAA, the Fund will include the combined awards of the Applicant and such Affiliated entities when calculating the amount of undisbursed award funds. For purposes of the calculation of undisbursed award funds for the BEA Program, only awards made to the Applicant (and any entity that Controls the Applicant, is Controlled by the Applicant or shares common management officials with the Applicant, as determined by the Fund) three to five calendar years prior to the end of the calendar year of the application deadline of this NOAA are included (“includable BEA awards”). Thus, for purposes of this NOAA, undisbursed BEA Program award funds are the amount of FYs 2003, 2004 and 2005 awards that remain undisbursed as of the application deadline of this NOAA. For purposes of the calculation of undisbursed award funds for the CDFI Program and the Native Initiatives Funding Programs, only awards made to the Applicant (and any entity that Controls the Applicant, is Controlled by the Applicant or shares common management officials with the Applicant, as determined by the Fund) two to five calendar years prior to the end of the calendar year of the application deadline of this NOAA are included (“includable CDFI/NI awards”). Thus, for purposes of this NOAA, undisbursed CDFI Program and NI awards are the amount of FYs 2003, 2004, 2005 and 2006 awards that remain undisbursed as of the application deadline of this NOAA. To calculate total includable BEA/CDFI/NI awards: amounts that are undisbursed as of the application deadline of this NOAA cannot exceed five percent (5%) of the total includable awards. Please refer to an example of this calculation in the 2008 Allocation Application Q&A document, available on the Fund's website. The “undisbursed award funds” calculation does not include:
(i)Tax credit allocation authority made available through the New Market Tax Credit
(NMTC)Program;
(ii)any award funds for which the Fund received a full and complete disbursement request from the Awardee (or any entity that Controls the Applicant, is Controlled by the Applicant or shares common management officials with the Applicant (as determined by the Fund) by the applicable application deadline of this NOAA;
(iii)any award funds for an award that has been terminated in writing by the Fund or deobligated by the Fund; or
(iv)any award funds for an award that does not have a fully executed assistance or award agreement. The Fund strongly encourages Applicants requesting disbursements of “undisbursed funds” from prior awards to provide the Fund with a complete disbursement request at least 30 business days prior to the application deadline of this NOAA. An Applicant that is unsure about the disbursement status of any prior award should contact the Fund's Financial Manager via e-mail at *CDFI.disburseinquiries@cdfi.treas.gov* for more information. Requests submitted less than thirty calendar days prior to the application deadline may not receive a response before the application deadline.
(g)*Contact the Fund* : Accordingly, applicants that are prior awardees and/or Allocatees under any other Fund program are advised to:
(i)Comply with the requirements specified in assistance, allocation and/or award agreement(s), and
(ii)contact the Fund to ensure that all necessary actions are underway for the disbursement of any outstanding balance of a prior award(s). All outstanding reports and compliance questions should be directed to the Compliance Manager by e-mail at *cme@cdfi.treas.gov* and all disbursement questions should be directed to the Grants Manager by e-mail at *grantsmanagement@cdfi.treas.gov* . Both the Compliance Manager and the Grants Manager can be reached by telephone at
(202)622-8226; by facsimile at
(202)622-6453; or by mail to CDFI Fund, 601 13th Street, NW., Suite 200 South, Washington, DC 20005. The Fund will respond to applicants' reporting, compliance or disbursement questions between the hours of 9 a.m. and 5 p.m. ET, starting the date of publication of this NOAA through March 3, 2008 (2 days before the application deadline). The Fund will not respond to applicants' reporting, compliance or disbursement phone calls or e-mail inquiries that are received after 5 p.m. ET on March 3, 2008 until after the funding application deadline of March 5, 2008. 3. *Entities that propose to transfer NMTCs to Subsidiaries:* Both for-profit and non-profit CDEs may apply to the Fund for allocations of NMTCs, but only a for-profit CDE is permitted to provide NMTCs to its investors. A non-profit applicant wishing to apply for a NMTC Allocation must demonstrate, prior to entering into an Allocation Agreement with the Fund, that:
(i)It controls one or more Subsidiaries that are for-profit entities; and
(ii)it intends to transfer the full amount of any NMTC Allocation it receives to said Subsidiary. The non-profit applicant should submit a CDE certification application to the Fund on behalf of the Subsidiary within 30 days after the non-profit applicant receives a Notice of Allocation from the Fund; as such Subsidiary must be certified as a CDE prior to entering into an Allocation Agreement with the Fund. The NMTC Allocation transfer must be pre-approved by the Fund, in its sole discretion, and will be a condition of the Allocation Agreement. A for-profit applicant that receives a NMTC Allocation may transfer such NMTC Allocation to its for-profit Subsidiary or Subsidiaries, provided that said Subsidiary transferees have been certified as CDEs and such transfer is pre-approved by the Fund, in its sole discretion. Any approved transfer will be included in the Allocation Agreement. An applicant wishing to transfer all or a portion of its NMTC Allocation to a Subsidiary is not required to create the Subsidiary prior to submitting a NMTC allocation application to the Fund. Rather, the Fund will require each applicant to indicate, in its NMTC allocation application, whether it intends to transfer all or a portion of its NMTC Allocation to a Subsidiary and its timeline for doing so. As stated above, in no circumstance will the Fund authorize such a transfer until the Fund has certified the Subsidiary transferee as a CDE. 4. *Entities that submit applications together with Affiliates; applications from common enterprises* :
(a)As part of the allocation application review process, the Fund considers whether applicants are Affiliates, as such term is defined in the allocation application. If an applicant and its Affiliates wish to submit allocation applications, they must do so collectively, in one application; an applicant and its Affiliates may not submit separate allocation applications. If Affiliated entities submit multiple applications, the Fund reserves the right either to reject all such applications received or to select a single application as the only one that will be considered for an allocation. For purposes of this NOAA, in addition to assessing whether applicants meet the definition of the term “Affiliate” found in the allocation application, the Fund will consider:
(i)Whether the activities described in applications submitted by separate entities are, or will be, operated or managed as a common enterprise that, in fact or effect, could be viewed as a single entity;
(ii)whether the applications submitted by separate entities contain significant narrative, textual or other similarities, and
(iii)whether the business strategies and/or activities described in applications submitted by separate entities are so closely related that, in fact or effect, they could be viewed as substantially identical applications. In such cases, the Fund reserves the right either to reject all applications received from all such entities; to select a single application as the only one that will be considered for an allocation; and, in the event that an application is selected to receive an allocation award, to deem certain activities ineligible.
(b)Furthermore, an applicant that receives an allocation in this allocation round (or its Subsidiary transferee) may not become an Affiliate of or member of a common enterprise (as defined above) with another applicant that receives an allocation in this allocation round (or its Subsidiary transferee) at any time after the submission of an allocation application under this NOAA. This prohibition, however, generally does not apply to entities that are commonly Controlled solely because of common ownership by QEI investors. This requirement will also be a term and condition of the Allocation Agreement (see section VI.B. of this NOAA and additional application guidance materials on the Fund's Web site at *http://www.cdfifund.gov* for more details). 5. *Entities created as a series of funds:* An applicant whose business structure consists of an entity with a series of funds may apply for CDE certification as a single entity, or as multiple entities. If such an applicant represents that it is properly classified for Federal tax purposes as a single partnership or corporation, it may apply for CDE certification as a single entity. If an applicant represents that it is properly classified for Federal tax purposes as multiple partnerships or corporations, then it may submit a single CDE certification application on behalf of the entire series of funds, and each fund must be separately certified as a CDE. Applicants should note, however, that receipt of CDE certification as a single entity or as multiple entities is not a determination that an applicant and its related funds are properly classified as a single entity or as multiple entities for Federal tax purposes. Regardless of whether the series of funds is classified as a single partnership or corporation or as multiple partnerships or corporations, an applicant may not transfer any NMTC Allocations it receives to one or more of its funds unless the transfer is pre-approved by the Fund, in its sole discretion, which will be a condition of the Allocation Agreement. 6. *Entities that are BEA Program awardees:* An insured depository institution investor (and its Affiliates and Subsidiaries) may not receive a NMTC Allocation in addition to a BEA Program award for the same investment in a CDE. Likewise, an insured depository institution investor (and its Affiliates and Subsidiaries) may not receive a BEA Program award in addition to a NMTC Allocation for the same investment in a CDE. IV. Application and Submission Information A. *Address to request application package:* Applicants must submit applications electronically under this NOAA, through the Fund website. Shortly following the publication of this NOAA, the Fund will make available the electronic allocation application on its Web site at *http://www.cdfifund.gov.* Applications sent by mail, facsimile or other form will not be accepted. The Fund will not accept applications in paper form, other than the assigned signature page and certain paper attachments, as specified below and in the application. B. *Application content requirements:* Detailed application content requirements are found in the application related to this NOAA. Applicants must submit all materials described in and required by the application by the applicable deadlines. Applicants will not be afforded an opportunity to provide any missing materials or documentation. Electronic applications must be submitted solely by using the format made available at the Fund's website. Additional information, including instructions relating to the submission of signature forms and supporting information, is set forth in further detail in the electronic application. An application must include a valid and current Employer Identification Number
(EIN)issued by the Internal Revenue Service and assigned to the applicant and, if applicable, it's Controlling Entity; electronic applications without a valid EIN are incomplete and cannot be transmitted to the Fund. For more information on obtaining an EIN, please contact the Internal Revenue Service at
(800)829-4933 or *http://www.irs.gov.* An applicant may not submit more than one application in response to this NOAA. In addition, as stated in section III.A.4 of this NOAA, an applicant and its Affiliates must collectively submit only one allocation application; an applicant and its Affiliates may not submit separate allocation applications. Once an application is submitted, an applicant will not be allowed to change any element of its application. C. *Form of application submission:* Applicants may only submit applications under this NOAA electronically. Applications sent by facsimile or by e-mail will not be accepted. Submission of an electronic application will facilitate the processing and review of applications and the selection of Allocatees; further, it will assist the Fund in the implementation of electronic reporting requirements. 1. *Electronic applications:* Electronic applications must be submitted solely by using the Fund's website and must be sent in accordance with the submission instructions provided in the electronic application form. Applicants need access to Internet Explorer 5.5 or higher or Netscape Navigator 6.0 or higher, Windows 98 or higher (or other system compatible with the above Explorer and Netscape software) and optimally at least a 56Kbps Internet connection in order to meet the electronic application submission requirements. The Fund's electronic application system will only permit the submission of applications in which all required questions and tables are fully completed. Additional information, including instructions relating to the submission of signature forms and supporting information, is set forth in further detail in the electronic application. D. *Application Submission Dates and Times:* 1. Application Deadlines:
(a)Electronic applications must be received by 5 p.m. ET on March 5, 2008. Electronic applications cannot be transmitted or received after 5 p.m. ET on March 5, 2008. In addition, applicants that submit electronic applications must separately submit (by mail or other courier delivery service) an original signature page, and all other required paper attachments. The original signature page and additional documents must be postmarked on or before March 7, 2008. See application instructions, provided in the electronic application, for further detail. Applications and other required documents and other attachments postmarked or received after these dates and times will be rejected. If the original signature page is not postmarked by the deadlines specified above, the application will be rejected. See section IV.D.1.(c) of this NOAA for further requirements relating to postmarks. Additional deadlines (if any) relating to the submission of general supporting documentation will be further detailed in the electronic application. Please note that the document submission deadlines in this NOAA and/or the allocation application are strictly enforced.
(b)For purposes of this NOAA, the term “postmark” is defined by 26 CFR 301.7502-1. In general, the Fund will require that the postmarked document bear a postmark date that is on or before the applicable deadline. The document must be in an envelope or other appropriate wrapper, properly addressed as set forth in this NOAA and delivered by the United States Postal Service or any other private delivery service designated by the Secretary of the Treasury. For more information on designated delivery services, please see IRS Notice 2002-62, 2002-2 C.B. 574. *E. Intergovernmental Review:* Not applicable. F. *Funding Restrictions:* For allowable uses of investment proceeds related to a NMTC Allocation, please see 26 U.S.C. 45D and the final regulations issued by the Internal Revenue Service (26 CFR 1.45D-1, published on December 28, 2004) and related guidance. Please see section I, above, for the Programmatic Improvements of this NOAA. *G. Other Submission Requirements:* 1. *Addresses:* The signature page and attachments for electronic applications must be sent as directed in the application materials to the Bureau of Public Debt, the application intake coordinator for the Fund. The signature page or attachments will not be accepted at the Fund's offices in Washington, DC. Signature pages or attachments received in the Fund's offices will be rejected. Except for the signature page and attachments, electronic applications must be submitted solely by using the Fund's website and must be sent in accordance with the submission instructions provided in the electronic application form. V. Application Review Information There are two parts to the substantive review process for each allocation application: Phase 1 and Phase 2. In Phase 1, the Fund will evaluate each application, assigning points and numeric scores with respect to the criteria described below. In Phase 2, the Fund will rank applicants in accordance with the procedures set forth below. A. *Criteria:* 1. *Business Strategy* (25-point maximum).
(a)In assessing an applicant's business strategy, reviewers will consider, among other things: the applicant's products, services and investment criteria; the prior performance of the applicant or its Controlling Entity, particularly as it relates to making similar kinds of investments as those it proposes to make with the proceeds of QEIs; the applicant's prior performance in providing capital or technical assistance to disadvantaged businesses or communities; the projected level of the applicant's pipeline of potential investments; and the extent to which the applicant intends to make Qualified Low-Income Community Investments (QLICIs) in one or more businesses in which persons unrelated to the entity hold a majority equity interest. Under the Business Strategy criterion, an applicant will generally score well to the extent that it will deploy debt or investment capital in products or services which:
(i)Are designed to meet the needs of underserved markets;
(ii)are flexible or non-traditional in form and on better terms than available in the marketplace; and
(iii)focus on customers or partners that typically lack access to conventional sources of capital. An applicant will also score well to the extent that it:
(i)Has a track record of successfully providing products and services similar to those it intends to use with the proceeds of QEIs;
(ii)has identified, or has a process for identifying, potential transactions;
(iii)demonstrates a likelihood of issuing QEIs and making the related QLICIs in a time period that is significantly shorter than the 5-year period permitted under IRC§ 45D(b)(1); and
(iv)in the case of an applicant proposing to purchase loans from CDEs, the applicant will require the CDE selling such loans to re-invest the proceeds of the loan sale to provide additional products and services to Low-Income Communities.
(b)*Priority Points:* In addition, as provided by IRC 45D(f)(2), the Fund will ascribe additional points to entities that meet either or both of the statutory priorities. First, the Fund will give up to five
(5)additional points to any applicant that has a record of having successfully provided capital or technical assistance to disadvantaged businesses or communities. Second, the Fund will give five
(5)additional points to any applicant that intends to satisfy the requirement of IRC 45D(b)(1)(B) by making QLICIs in one or more businesses in which persons unrelated (within the meaning of IRC 267(b) or IRC 707(b)(1)) to an applicant (or the applicant's subsidiary CDEs) hold the majority equity interest. Applicants may earn points for either or both statutory priorities. Thus, applicants that meet the requirements of both priority categories can receive up to a total of ten
(10)additional points. A record of having successfully provided capital or technical assistance to disadvantaged businesses or communities may be demonstrated either by the past actions of an applicant itself or by its Controlling Entity ( *e.g.* , where a new CDE is established by a nonprofit corporation with a history of providing assistance to disadvantaged communities). An applicant that receives additional points for intending to make investments in unrelated businesses and is awarded a NMTC Allocation must meet the requirements of IRC 45D(b)(1)(B) by investing substantially all of the proceeds from its QEIs in unrelated businesses. The Fund will factor in an applicant's priority points when ranking applicants during Phase 2 of the review process, as described below. 2. *Community Impact* (25-point maximum). In assessing the impact on communities expected to result from the applicant's proposed investments, reviewers will consider, among other things, the degree to which the applicant is likely to achieve significant and measurable community development and economic impacts in its Low-Income Communities, and whether the applicant is working in particularly economically distressed markets and/or in concert with Federal, state or local government or community economic development initiatives ( *e.g.* , Empowerment Zones, Enterprise Communities, and Renewal Communities). An applicant will generally score well under this section to the extent that:
(a)It articulates how its strategy is likely to produce significant and measurable community development and economic impacts that would not be achieved without NMTCs; and
(b)it is working in particularly economically distressed or otherwise underserved communities and/or in concert with other Federal, state or local government or community economic development initiatives. 3. *Management Capacity* (25-point maximum). In assessing an applicant's management capacity, reviewers will consider, among other things, the qualifications of the applicant's principals, its board members, its management team, and other essential staff or contractors, with specific focus on: Experience in deploying capital or technical assistance, including activities similar to those described in the applicant's business strategy; experience in raising capital; asset management and risk management experience; experience with fulfilling compliance requirements of other governmental programs, including other tax programs; and the applicant's (or its Controlling Entity's) financial health. Reviewers will also consider the extent to which an applicant has protocols in place to ensure ongoing compliance with NMTC Program requirements and the level of involvement of community representatives and other stakeholders in the design, implementation or monitoring of an applicant's business plan and strategy. In the case of an applicant (or any entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant, as determined by the Fund) that has received a NMTC Allocation from the Fund under a prior allocation round, reviewers will consider the activities that have occurred to date with respect to the prior allocation(s). An applicant will generally score well under this section to the extent that its management team or other essential personnel have experience in:
(a)Deploying capital or technical assistance in Low-Income Communities, particularly those likely to be served by the applicant with the proceeds of QEIs;
(b)raising capital, particularly from for-profit investors;
(c)asset and risk management; and
(d)fulfilling government compliance requirements, particularly tax program compliance. An applicant will also score well to the extent it has policies and systems in place to ensure ongoing compliance with NMTC Program requirements, and to the extent that Low-Income Community stakeholders play an active role in designing or implementing its business plan. In the case of an applicant (or any entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant, as determined by the Fund) that has received a NMTC Allocation from the Fund under a prior allocation round, the applicant will score well to the extent it can:
(a)Demonstrate that substantial activities have occurred through its prior allocation(s); and
(b)substantiate a need for additional allocation authority. 4. *Capitalization Strategy* (25-point maximum). In assessing an applicant's capitalization strategy, reviewers will consider, among other things: the extent to which the applicant has secured investments, commitments to invest, or indications of interest in investments from investors, commensurate with its requested amount of tax credit allocations; the applicant's strategy for identifying additional investors, if necessary, including the applicant's (or its Controlling Entity's) prior performance with raising equity from investors, particularly for-profit investors; the extent to which the applicant identifies how existing investors will leverage their investments in Low-Income Communities or how new investors will be brought into such investments; the distribution of the economic benefits of the tax credit; the extent to which the applicant intends to invest the proceeds from the aggregate amount of its QEIs at a level that exceeds the requirements of IRC 45D(b)(1)(B) and the IRS regulations, including the extent to which the applicant has identified the financial resources outside of the NMTC investments necessary to support its operations or finance its activities; and the applicant's timeline for utilizing an NMTC Allocation. An applicant will generally score well under this section to the extent that:
(a)It has secured investor commitments, or has a reasonable strategy for obtaining such commitments;
(b)its request for allocations is commensurate with both the level of QEIs it is likely to raise and its expected investment strategy to deploy funds raised with NMTCs;
(c)it generally demonstrates that the economic benefits of the tax credit will be passed through to end users;
(d)it is likely to leverage other sources of funding in addition to NMTC investor dollars; and
(e)it intends to invest the proceeds from the aggregate amount of its QEIs at a level that exceeds the requirements of IRC 45D(b)(1)(B) and the IRS regulations. In the case of an applicant proposing to raise investor funds from organizations that also will identify or originate transactions for the applicant or from affiliated entities, said applicant will score well to the extent that it will offer products with more favorable rates or terms than those currently offered by the investor and/or will target its activities to areas of greater economic distress than those currently targeted by the investor. B. *Review and selection process* : All allocation applications will be reviewed for eligibility and completeness. The Fund may consult with the IRS on the eligibility requirements under IRC 45D. To be complete, the application must contain, at a minimum, all information described as required in the application form. An incomplete application will be rejected. Once the application has been determined to be eligible and complete, the Fund will conduct the substantive review of each application in two parts (Phase 1 and Phase 2) in accordance with the criteria and procedures generally described in this NOAA and the allocation application. 1. *Phase 1* : Fund reviewers will evaluate and score each application in the first part of the review process. An applicant must exceed a minimum overall aggregate base score threshold and exceed a minimum aggregate section score threshold in each of the four application sections (Business Strategy, Community Impact, Management Capacity, and Capitalization Strategy) in order to advance from the first part of the substantive review process. If, in the case of a particular application, a reviewer's total base score or section score(s) (in one or more of the four application sections), varies significantly from the median of the reviewers' total base scores or section scores for such application, the Fund may, in its sole discretion, obtain the comments and recommendations of an additional reviewer to determine whether the anomalous score should be replaced with the score of the additional reviewer. 2. *Phase 2* : Once the Fund has determined which applicants have met the required minimum overall aggregate base score and aggregate section score thresholds, the Fund will rank applicants on the basis of their combined scores in the Business Strategy and Community Impact sections of the application and will make adjustments to each applicant's priority points so that these points maintain the same relative weight in the ranking of applicant scores in Phase 2 as in Phase 1. The Fund will award allocations in the order of this “Final Rank Score,” subject to applicants” meeting all other eligibility requirements; provided, however, that the Fund, in its sole discretion, reserves the right to reject an application and/or adjust award amounts as appropriate based on information obtained during the review process. 3. *Outstanding Reports* . In the case of an applicant (or any entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant, (as determined by the Fund) that has previously received an award or allocation from the Fund through any Fund program, the Fund will consider and will deduct points for the applicant's (or any entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant, as determined by the Fund) failure to meet the reporting deadlines set forth in any assistance, award or Allocation Agreement(s) with the Fund during the applicant's two complete fiscal years prior to the application deadline of this NOAA (generally FY 2006 and 2007). C. *Allocations serving Non-Metropolitan counties* . As discussed in Part I, the Fund will ensure that the proportion of allocatees that are Rural CDEs is, at a minimum, equal to the proportion of applicants in the Phase 2 review pool that are Rural CDEs; and ensure that at least 20 percent of the QLICIs to be made using QEI proceeds are invested in Non-Metropolitan counties. As stated earlier, a Rural CDE is one that has over the past five years dedicated at least 50 percent of its activities to Non-Metropolitan counties and has committed that at least 50 percent of its NMTC activities will be conducted in such areas. Non-Metropolitan counties are counties not contained within a Metropolitan Statistical Area, as such term is defined in OMB Bulletin No. 99-04 (Revised Statistical Definitions of Metropolitan Areas
(MAs)and Guidance on Uses of MA Definitions) and applied using 2000 census data. The Fund will not make changes with respect to the initial Phase 1 review and scoring process in order to achieve these outcomes. Rather, adjustments will be made during the Phase 2 review process, as needed. Applicants that meet the minimum scoring thresholds will be advanced to Phase 2 review and will be provided with “preliminary” awards, in descending order of Final Rank Score, until the $3.5 billion in allocation authority is expended. Once these “preliminary” award amounts are determined, the Fund will then analyze the allocatee pool to determine whether the two Non-Metropolitan proportionality objectives have been met. The Fund will first examine the “preliminary” awards and allocatees to determine whether the percentage of allocatees that are Rural CDEs is, at a minimum, equal to the percentage of applicants in the Phase 2 review pool that are Rural CDEs. If this objective is not achieved, the Fund will provide awards to additional Rural CDEs from the Phase 2 pool, in descending order of their Final Rank Score, until the appropriate percentage balance is achieved. In order to accommodate the additional allocatees within the $3.5 billion allocation limitations, a formula reduction will be applied uniformly to the allocation amount for all allocatees in the pool. The Fund will then ensure that the pool of allocatees will, in the aggregate, invest at least 20 percent of their QLICIs (as measured by dollar amount) in Non-Metropolitan counties. The Fund will first apply the “minimum” percentage of QLICIs that allocatees indicated in their applications would be targeted to Non-Metropolitan areas to the total allocation award amount of each allocatee (less whatever percentage the allocatee indicated would be retained for non-QLICI activities), and total these figures for all allocatees. If this aggregate total is greater than or equal to 20 percent of the QLICIs to be made by the allocatees, then the pool is considered balanced and the Fund will proceed with the allocation process. If, however, the aggregate total is less than 20 percent of the QLICIs to be made by the allocatees, the Fund will consider requiring any or all of the Allocatees to direct up to the “maximum” percentage of QLICIs that they indicated would be targeted to Non-Metropolitan counties; taking into consideration their track record and ability to deploy dollars in Non-Metropolitan counties. D. All outstanding reports or compliance questions should be directed to the Compliance Manager by e-mail at *cme@cdfi.treas.gov* ; by telephone at
(202)622-8226; by facsimile at
(202)622-6453; or by mail to CDFI Fund, 601 13th Street, NW., Suite 200 South, Washington, DC 20005. The Fund will respond to reporting or compliance questions between the hours of 9 a.m. and 5 p.m. ET, starting the date of the publication of this NOAA through March 3, 2008. The Fund will not respond to reporting or compliance phone calls or e-mail inquiries that are received after 5 p.m. ET on March 3, 2008 until after the funding application deadline of March 5, 2008. E. The Fund reserves the right to reject any NMTC allocation application in the case of a prior Fund awardee, if such applicant has failed to comply with the terms, conditions, and other requirements of the prior or existing assistance or award agreement(s) with the Fund. The Fund reserves the right to reject any NMTC allocation application in the case of a prior Fund Allocatee, if such applicant has failed to comply with the terms, conditions, and other requirements of its prior or existing Allocation Agreement(s) with the Fund. The Fund reserves the right to reject any NMTC allocation application in the case of any applicant, if an entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant (as determined by the Fund), has failed to meet the terms, conditions and other requirements of any prior or existing assistance agreement, award agreement or Allocation Agreement with the Fund. The Fund reserves the right to reject any NMTC allocation application in the case of a prior Fund Allocatee, if such applicant has failed to use its prior NMTC allocation(s) in a manner that is generally consistent with the business strategy (including, but not limited to, the proposed product offerings and markets served) set forth in the allocation application(s) related to such prior allocation(s). The Fund also reserves the right to reject any NMTC allocation application in the case of any applicant, if an entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant (as determined by the Fund), is a prior Fund Allocatee and has failed to use its prior NMTC allocation(s) in a manner that is generally consistent with the business strategy set forth in the allocation application(s) related to such prior allocation(s). The Fund also reserves the right to reject a NMTC allocation application if information (including administrative errors) comes to the attention of the Fund that adversely affects an applicant's eligibility for an award, adversely affects the Fund's evaluation or scoring of an application, or indicates fraud or mismanagement on the part of an applicant. If the Fund determines that any portion of the application is incorrect in any material respect, the Fund reserves the right, in its sole discretion, to reject the application. As a part of the substantive review process, the Fund may permit reviewer(s) to make telephone calls to applicants for the sole purpose of obtaining, clarifying or confirming application information. In no event shall such contact be construed to permit an applicant to change any element of its application. Reviewers will not contact applicants without the prior approval of the Fund. At this point in the process, an applicant may be required to submit additional information about its application in order to assist the Fund with its final evaluation process. Such requests must be responded to within the time parameters set by the Fund. The selecting official(s) will make a final allocation determination based on an applicant's file, including without limitation, eligibility under IRC 45D, the reviewers' scores and the amount of allocation authority available. In the case of applicants (or any entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant, as determined by the Fund) that are regulated by the Federal government or a State agency (or comparable entity), the Fund's selecting official(s) reserve(s) the right to consult with and take into consideration the views of the appropriate Federal or State banking and other regulatory agencies. In the case of applicants (or any entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant, as determined by the Fund) that are also Small Business Investment Companies, Specialized Small Business Investment Companies or New Markets Venture Capital Companies, the Fund reserves the right to consult with and take into consideration the views of the Small Business Administration. The Fund reserves the right to conduct additional due diligence, as determined reasonable and appropriate by the Fund, in its sole discretion, related to the applicant and its officers, directors, owners, partners and key employees. Each applicant will be informed of the Fund's award decision either through a Notice of Allocation if selected for an allocation (see section VI.A. of this NOAA) or a declination letter, if not selected for an allocation, which may be for reasons of application incompleteness, ineligibility or substantive issues. All applicants that are not selected for an allocation based on substantive issues will likely be given the opportunity to obtain feedback on the strengths and weaknesses of their applications. This feedback will be provided in a format and within a timeframe to be determined by the Fund, based on available resources. The Fund further reserves the right to change its eligibility and evaluation criteria and procedures, if the Fund deems it appropriate. If said changes materially affect the Fund's award decisions, the Fund will provide information regarding the changes through the Fund's website. There is no right to appeal the Fund's allocation decisions. The Fund's allocation decisions are final. VI. Award Administration Information A. *Notice of Allocation:* The Fund will signify its selection of an applicant as an Allocatee by delivering a signed Notice of Allocation to the applicant. The Notice of Allocation will contain the general terms and conditions underlying the Fund's provision of an NMTC Allocation including, but not limited to, the requirement that an Allocatee and the Fund enter into an Allocation Agreement. The applicant must execute the Notice of Allocation and return it to the Fund. By executing a Notice of Allocation, the Allocatee agrees that, if prior to entering into an Allocation Agreement with the Fund, information (including administrative errors) comes to the attention of the Fund that adversely affects the Allocatee's eligibility for an award, adversely affects the Fund's evaluation or scoring of the Allocatee's application, or indicates fraud or mismanagement on the part of the Allocatee, the Fund may, in its discretion and without advance notice to the Allocatee, terminate the Notice of Allocation or take such other actions as it deems appropriate. Moreover, by executing a Notice of Allocation, an Allocatee agrees that, if prior to entering into an Allocation Agreement with the Fund, the Fund determines that the Allocatee is not in compliance with the terms of any prior assistance agreement, award agreement, and/or Allocation Agreement entered into with the Fund, the Fund may, in its discretion and without advance notice to the Allocatee, either terminate the Notice of Allocation or take such other actions as it deems appropriate. The Fund reserves the right, in its sole discretion, to rescind the allocation and the Notice of Allocation if the Allocatee fails to return the Notice of Allocation, signed by the authorized representative of the Allocatee, along with any other requested documentation, by the deadline set by the Fund. 1. *Failure to meet reporting requirements:* If an Allocatee, or an entity that Controls the Allocatee, is Controlled by the Allocatee or shares common management officials with the Allocatee (as determined by the Fund) is a prior Fund awardee or Allocatee under any Fund program and is not current on the reporting requirements set forth in the previously executed assistance, allocation or award agreement(s), as of the date of the Notice of Allocation or thereafter, the Fund reserves the right, in its sole discretion, to delay entering into an Allocation Agreement and/or to impose limitations on an Allocatee's ability to issue QEIs to investors until said prior awardee or Allocatee is current on the reporting requirements in the previously executed assistance, allocation or award agreement(s). Please note that the Fund only acknowledges the receipt of reports that are complete. As such, incomplete reports or reports that are deficient of required elements will not be recognized as having been received. If said prior awardee or Allocatee is unable to meet this requirement within the timeframe set by the Fund, the Fund reserves the right, in its sole discretion, to terminate and rescind the Notice of Allocation and the allocation made under this NOAA. 2. *Pending resolution of noncompliance:* If an applicant is a prior awardee or Allocatee under any Fund program and if:
(i)It has submitted complete and timely reports to the Fund that demonstrate noncompliance with a previous assistance, award or Allocation Agreement; and
(ii)the Fund has yet to make a final determination as to whether the entity is in default of its previous assistance, award or Allocation Agreement, the Fund reserves the right, in its sole discretion, to delay entering into an Allocation Agreement and/or to impose limitations on the Allocatee's ability to issue Qualified Equity Investments to investors, pending full resolution, in the sole determination of the Fund, of the noncompliance. Further, if another entity that Controls the applicant, is Controlled by the applicant or shares common management officials with the applicant (as determined by the Fund), is a prior Fund awardee or Allocatee and if such entity:
(i)Has submitted complete and timely reports to the Fund that demonstrate noncompliance with a previous assistance, award or Allocation Agreement; and
(ii)the Fund has yet to make a final determination as to whether the entity is in default of its previous assistance, award or Allocation Agreement, the Fund reserves the right, in its sole discretion, to delay entering into an Allocation Agreement and/or to impose limitations on the Allocatee's ability to issue QEIs to investors, pending full resolution, in the sole determination of the Fund, of the noncompliance. If the prior awardee or Allocatee in question is unable to satisfactorily resolve the issues of noncompliance, in the sole determination of the Fund, the Fund reserves the right, in its sole discretion, to terminate and rescind the Notice of Allocation and the allocation made under this NOAA. 3. *Default status:* If, at any time prior to entering into an Allocation Agreement through this NOAA, the Fund has made a final determination that an Allocatee that is a prior Fund awardee or Allocatee under any Fund program is in default of a previously executed assistance, allocation or award agreement(s) and has provided written notification of such determination to the Allocatee, the Fund reserves the right, in its sole discretion, to delay entering into an Allocation Agreement and/or to impose limitations on the Allocatee's ability to issue QEIs to investors, until said prior awardee or Allocatee has submitted a complete and timely report demonstrating full compliance with said agreement within a timeframe set by the Fund. Further, if at any time prior to entering into an Allocation Agreement through this NOAA, the Fund has made a final determination that another entity that Controls the Allocatee, is Controlled by the applicant or shares common management officials with the Allocatee (as determined by the Fund), is a prior Fund awardee or Allocatee under any Fund program, and is in default of a previously executed assistance, allocation or award agreement(s) and has provided written notification of such determination to the defaulting entity, the Fund reserves the right, in its sole discretion, to delay entering into an Allocation Agreement and/or to impose limitations on the Allocatee's ability to issue QEIs to investors, until said prior awardee or Allocatee has submitted a complete and timely report demonstrating full compliance with said agreement within a timeframe set by the Fund. If said prior awardee or Allocatee is unable to meet this requirement, the Fund reserves the right, in its sole discretion, to terminate and rescind the Notice of Allocation and the allocation made under this NOAA. 4. *Termination in default* : If
(i)within the 12-month period prior to entering into an Allocation Agreement through this NOAA, the Fund has made a final determination that an Allocatee that is a prior Fund awardee or Allocatee under any Fund program whose award or allocation was terminated in default of such prior agreement;
(ii)the Fund has provided written notification of such determination to such organization; and
(iii)the final reporting period end date for the applicable terminated agreement falls in such organization's 2006 or 2007 fiscal year, the Fund reserves the right, in its sole discretion, to delay entering into an Allocation Agreement and/or to impose limitations on the Allocatee's ability to issue QEIs to investors. Further, if
(i)within the 12-month period prior to entering into an Allocation Agreement through this NOAA, the Fund has made a final determination that another entity that Controls the Allocatee, is Controlled by the Allocatee or shares common management officials with the Allocatee (as determined by the Fund), is a prior Fund awardee or Allocatee under any Fund program whose award or allocation was terminated in default of such prior agreement;
(ii)the Fund has provided written notification of such determination to the defaulting entity; and
(iii)the final reporting period end date for the applicable terminated agreement falls in such defaulting entity's 2006 or 2007 fiscal year, the Fund reserves the right, in its sole discretion, to delay entering into an Allocation Agreement and/or to impose limitations on the Allocatee's ability to issue QEIs to investors. B. *Allocation Agreement* : Each applicant that is selected to receive a NMTC Allocation (including the applicant's Subsidiary transferees) must enter into an Allocation Agreement with the Fund. The Allocation Agreement will set forth certain required terms and conditions of the NMTC Allocation which may include, but are not limited to, the following:
(i)The amount of the awarded NMTC Allocation;
(ii)the approved uses of the awarded NMTC Allocation ( *e.g.* , loans to or equity investments in Qualified Active Low-Income Businesses or loans to or equity investments in other CDEs);
(iii)the approved service area(s) in which the proceeds of QEIs may be used, including the dollar amount of QLICIs that must be invested in Non-Metropolitan counties;
(iv)the time period by which the applicant may obtain QEIs from investors;
(v)reporting requirements for all applicants receiving NMTC Allocations; and
(vi)a requirement to maintain certification as a CDE throughout the term of the Allocation Agreement. If an applicant has represented in its NMTC allocation application that it intends to invest substantially all of the proceeds from its investors in businesses in which persons unrelated to the applicant hold a majority equity interest, the Allocation Agreement will contain a covenant whereby said applicant agrees that it will invest substantially all of said proceeds in businesses in which persons unrelated to the applicant hold a majority equity interest. In addition to entering into an Allocation Agreement, each applicant selected to receive a NMTC Allocation must furnish to the Fund an opinion from its legal counsel, the content of which will be further specified in the Allocation Agreement, to include, among other matters, an opinion that an applicant (and its Subsidiary transferees, if any):
(i)Is duly formed and in good standing in the jurisdiction in which it was formed and the jurisdiction(s) in which it operates;
(ii)has the authority to enter into the Allocation Agreement and undertake the activities that are specified therein;
(iii)has no pending or threatened litigation that would materially affect its ability to enter into and carry out the activities specified in the Allocation Agreement; and
(iv)is not in default of its articles of incorporation, bylaws or other organizational documents, or any agreements with the Federal government. If an Allocatee identifies Subsidiary transferees, the Fund reserves the right to require an Allocatee to provide supporting documentation evidencing that it Controls such entities prior to entering into an Allocation Agreement with the Allocatee and its Subsidiary transferees. The Fund reserves the right, in its sole discretion, to rescind its Notice of Allocation if the Allocatee fails to return the Allocation Agreement, signed by the authorized representative of the Allocatee, and/or provide the Fund with any other requested documentation, within the deadlines set by the Fund. C. *Fees:* The Fund reserves the right, in accordance with applicable Federal law and if authorized, to charge allocation reservation and/or compliance monitoring fees to all entities receiving NMTC Allocations. Prior to imposing any such fee, the Fund will publish additional information concerning the nature and amount of the fee. D. *Reporting:* The Fund will collect information, on at least an annual basis, from all applicants that are awarded NMTC Allocations and/or are recipients of QLICIs, including such audited financial statements and opinions of counsel as the Fund deems necessary or desirable, in its sole discretion. The Fund will use such information to monitor each Allocatee's compliance with the provisions of its Allocation Agreement and to assess the impact of the NMTC Program in Low-Income Communities. The Fund may also provide such information to the IRS in a manner consistent with IRC 6103 so that the IRS may determine, among other things, whether the Allocatee has used substantially all of the proceeds of each QEI raised through its NMTC Allocation to make QLICIs. The Allocation Agreement shall further describe the Allocatee's reporting requirements. The Fund reserves the right, in its sole discretion, to modify these reporting requirements if it determines it to be appropriate and necessary; however, such reporting requirements will be modified only after due notice to Allocatees. VII. Agency Contacts The Fund will provide programmatic and information technology support related to the allocation application between the hours of 9 a.m. and 5 p.m. ET through March 3, 2008. The Fund will not respond to phone calls or e-mails concerning the application that are received after 5 p.m. ET on March 3, 2008 until after the allocation application deadline of March 5, 2008. Applications and other information regarding the Fund and its programs may be obtained from the Fund's Web site at *http://www.cdfifund.gov.* The Fund will post on its website responses to questions of general applicability regarding the NMTC Program. A. *Information technology support:* Technical support can be obtained by calling
(202)622-2455 or by e-mail at *ithelpdesk@cdfi.treas.gov.* People who have visual or mobility impairments that prevent them from accessing the Low-Income Community maps using the Fund's website should call
(202)622-2455 for assistance. These are not toll-free numbers. B. *Programmatic support:* If you have any questions about the programmatic requirements of this NOAA, contact the Fund's NMTC Program Manager by e-mail at *cdfihelp@cdfi.treas.gov,* by telephone at
(202)622-6355, by facsimile at
(202)622-7754, or by mail at CDFI Fund, 601 13th Street, NW., Suite 200 South, Washington, DC 20005. These are not toll-free numbers. C. *Administrative support:* If you have any questions regarding the administrative requirements of this NOAA, contact the Fund's Grants Manager by e-mail at *grantsmanagement@cdfi.treas.gov,* by telephone at
(202)622-8226, by facsimile at
(202)622-6453, or by mail at CDFI Fund, 601 13th Street, NW., Suite 200 South, Washington, DC 20005. These are not toll-free numbers. D. *IRS support:* For questions regarding the tax aspects of the NMTC Program, contact Branch Five, Office of the Associate Chief Counsel (Passthroughs and Special Industries), IRS, by telephone at
(202)622-3040, by facsimile at
(202)622-4753, or by mail at 1111 Constitution Avenue, NW., Attn: CC:PSI:5, Washington, DC 20224. These are not toll-free numbers. E. *Legal counsel support:* If you have any questions or matters that you believe require response by the Fund's Office of Legal Counsel, please refer to the document titled “How to Request a Legal Review,” found on the Fund's Web site at *http://www.cdfifund.gov.* VIII. Information Sessions In connection with this NOAA, the Fund intends to conduct multiple information sessions around the country at locations to be announced as well as an information session that will be produced in Washington, DC and broadcast over the internet via webcasting. For further information on these upcoming information sessions, please visit the Fund's Web site at *http://www.cdfifund.gov* or call the Fund at
(202)622-9046. Authority: 26 U.S.C. 45D; 31 U.S.C. 321; 26 CFR 1.45D-1. Dated: December 19, 2007. Donna Gambrell, Director, Community Development Financial Institutions Fund. [FR Doc. E7-25145 Filed 12-27-07; 8:45 am] BILLING CODE 4810-70-P DEPARTMENT OF THE TREASURY Internal Revenue Service Proposed Collection; Comment Request for Form 8609, 8609-A AGENCY: Internal Revenue Service (IRS), Treasury. ACTION: Notice and request for comments. SUMMARY: The Department of the Treasury, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on proposed and/or continuing information collections, as required by the Paperwork Reduction Act of 1995, Public Law 104-13 (44 U.S.C. 3506(c)(2)(A)). Currently, the IRS is soliciting comments concerning Form 8609, Low-Income Housing Credit Allocation and Certification and 8609-A, Annual Statement of Low-Income Housing Credit. DATES: Written comments should be received on or before February 26, 2008 to be assured of consideration. ADDRESSES: Direct all written comments to Glenn P. Kirkland, Internal Revenue Service, Room 6129, 1111 Constitution Avenue NW., Washington, DC 20224. FOR FURTHER INFORMATION CONTACT: Requests for additional information or copies of the form and instructions should be directed to R. Joseph Durbala at Internal Revenue Service, Room 6129, 1111 Constitution Avenue NW., Washington, DC 20224, or at
(202)622-3634, or through the Internet at *RJoseph.Durbala@irs.gov* . SUPPLEMENTARY INFORMATION: *Title:* Low-Income Housing Credit Allocation and Certification. *OMB Number:* 1545-0988. *Form Number:* Form 8609. *Title:* Annual Statement for Low-Income Housing Credit. *OMB Number:* 1545-0988. *Form Number:* Form 8609-A. *Abstract:* Owners of residential low-income rental buildings may claim a low-income housing credit for each qualified building over a 10-year credit period. Form 8609 and 8609-A are used to obtain a housing credit allocation from the housing credit agency. The form(s) are used by the owner to certify necessary information required by the law. *Current Actions:* There are no changes being made to the burden for Form 8609 or Form 8609-A at this time. *Type of Review:* Extension of a current OMB approval. *Affected Public:* Business or other for-profit organizations, individuals, and state, local or tribal governments. *Estimated Number of Respondents:* 120,000. *Estimated Time Per Respondent:* 29 hours., 11 minutes. *Estimated Total Annual Burden Hours:* 3,329,400. The following paragraph applies to all of the collections of information covered by this notice: An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless the collection of information displays a valid OMB control number. Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103. *Request for Comments:* Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record. Comments are invited on:
(a)Whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility;
(b)the accuracy of the agency's estimate of the burden of the collection of information;
(c)ways to enhance the quality, utility, and clarity of the information to be collected;
(d)ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology; and
(e)estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information. Approved: December 19, 2007. Glenn P. Kirkland, IRS Reports Clearance Officer. [FR Doc. E7-25126 Filed 12-27-07; 8:45 am] BILLING CODE 4830-01-P DEPARTMENT OF VETERANS AFFAIRS Advisory Committee on Homeless Veterans; Notice of Meeting The Department of Veterans Affairs
(VA)gives notice under Public Law 92-463 (Federal Advisory Committee Act) that a meeting of the Advisory Committee on Homeless Veterans will be held on January 31-February 1, 2008, in Room 630 at the Department of Veterans Affairs, 810 Vermont Avenue, NW., Washington, DC. On January 31, the session will begin at 8 a.m. and end at 4 p.m. and on February 1, the session will begin at 8 a.m. and end at 2:30 p.m. The meeting is open to the public. The purpose of the Committee is to provide the Secretary of Veterans Affairs with a continuing assessment of the effectiveness of the policies, organizational structures, and services of the Department in assisting homeless veterans. The Committee shall assemble and review information relating to the needs of homeless veterans and provide advice on the most appropriate means of offering assistance to homeless veterans. The Committee will make recommendations to the Secretary regarding such activities. The Committee will receive briefings from VA and other officials and begin final preparation of its upcoming annual report and recommendations to the Secretary. Those wishing to attend the meeting should give prior notice by contacting Mr. Pete Dougherty, Department of Veterans Affairs, at
(202)461-7401. No time will be allocated for receiving oral presentations from the public. However, the Committee will accept written comments from interested parties on issues affecting homeless veterans. Such comments should be referred to the Committee at the following address: Advisory Committee on Homeless Veterans, Homeless Veterans Programs Office (075D), U.S. Department of Veterans Affairs, 810 Vermont Avenue, NW., Washington, DC 20420. Dated: December 20, 2007. By Direction of the Secretary. E. Philip Riggin, Committee Management Officer. [FR Doc. 07-6235 Filed 12-27-07; 8:45 am]
Connectionstraces to 11
23 references not yet in our index
  • 23 CFR 668
  • 49 CFR 1.48
  • 23 CFR 645
  • 23 CFR 615.215
  • 49 CFR 240.117(e)(1)
  • 49 CFR 236.913(j)(1)
  • 5 CFR 1320.8(d)
  • 49 CFR 541
  • 15 USC 1392
  • Pub. L. 102-519
  • 49 CFR 580
  • 49 USC 32905-32906
  • 49 CFR 199.105(c)(2)
  • 49 CFR 199.119(a)
  • 49 CFR 1.53
  • 49 CFR 1244.9
  • Pub. L. 106-554
  • Pub. L. 108-357
  • Pub. L. 109-432
  • 26 CFR 1.45
  • 26 USC 45D
  • Pub. L. 104-13
  • Pub. L. 92-463
Citation graph
cites case law
Notices
Notice of request for extension of currently approved information collection
Cite23 CFR 668
Cite49 CFR 1.48
Cite23 CFR 645
Cites 34 · 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.