### 18255 Federal Register / Vol. 75, No. 68 / Friday, April 9, 2010 / Notices

Director of the Bureau of Transportation Statistics. Non-committee members wishing to present oral statements or obtain information should contact Ms. Winston via email no later than April 27, 2010.

Questions about the agenda or written comments may be emailed or submitted by U.S. Mail to: U.S. Department of Transportation, Research and Innovative Technology Administration, Bureau of Transportation Statistics, Attention: Chanel Winston, 1200 New Jersey Avenue, SE., Room # E34–455, Washington, DC 20590, or faxed to (202) 366–1270. BTS requests that written comments be received by April 30,

2010.

Notice of this meeting is provided in accordance with the FACA and the General Services Administration regulations (41 CFR part 102–3) covering management of Federal advisory committees.

Issued in Washington, DC, on the 2nd day of April 2010. Steven D. Dillingham, Director, Bureau of Transportation Statistics

[FR Doc. 2010–8109 Filed 4–8–10; 8:45 am]

**BILLING CODE 4910–HY–P**

**DEPARTMENT OF TRANSPORTATION**

**Federal Aviation Administration**

**[Docket No. FAA–2010]**

**Passenger Facility Charge Database System for Air Carrier Reporting** 

**AGENCY :**  Federal Aviation Administration (FAA), Department of Transportation (DOT).

**ACTION :**  Notice of availability.

**SUMMARY :**  The Federal Aviation Administration (FAA) is issuing this Notice of Availability to inform interested parties of the availability of the Passenger Facility Charge (PFC) database system to report PFC quarterly report information. In accordance with 14 CFR part 158.63, the public agency approved to collect PFCs must provide quarterly PFC reports to air carriers collecting PFCs for the public agency and the FAA. In accordance with § 158.65, each air carrier collecting PFCs for a public agency must provide quarterly reports to the public agency unless otherwise agreed to by the collecting air carrier and the public agency. The FAA has developed a national PFC database system in order to more easily track the PFC program on a nationwide basis. The PFC database system was developed in three phases. The first phase was a national internal database for FAA use. The second phase expanded the database to allow public agencies to enter and access the PFC quarterly reports for their airport(s). The third phase expands the system to provide database access to the air carriers. The first and second phases of the database are complete. The third phase will allow air carriers to enter PFC collection and remittance information directly into the PFC database on a monthly basis. Use of the PFC database is voluntary and is not the sole means of complying with sections 158.63 and 158.65. However, as stated in 158.20(b), once the air carriers have access to the FAA’s PFC database system, those air carriers and public agencies participating in the system will no longer be required to transmit quarterly reports to any interested party.

**DATES :**  The system will be fully available to all users (FAA, public agencies, and air carriers) on June 21,

2010.

**FOR FURTHER INFORMATION CONTACT :**  Jane Johnson, Financial Analysis and Passenger Facility Charge Branch (APP– 510), Room 619, Federal Aviation Administration, 800 Independence Avenue, SW., Washington, DC 20591; telephone: (202) 267–5878, e-mail: 9- AWA-ARP-APP-PFC-Info@FAA.GOV.

**SUPPLEMENTARY INFORMATION :**  The PFC program is codified in Title 49 United States Code (U.S.C.) § 40117 and is implemented by 14 CFR part 158. The PFC program provides an important and independent source of financing for the needs of U.S. commercial service airports through an airport enplanement charge per passenger of $1, $2, $3, $4, or $4.50 per trip segment up to amaximum of two segments on a oneway trip and four segments on a round trip. Air carriers collect and remit the PFC fees directly to an eligible public agency authorized by the FAA in accordance with statutory and regulatory requirements to impose a PFC at a commercial service airport(s) it controls.

Under part 158, public agencies controlling commercial service airports can apply to the FAA for authority to impose and/or use a PFC to finance approved, eligible airport related projects. Section 158.3 defines a public agency to be a state or any agency or one or more states: a municipality or other political subdivision of a state; an authority created by Federal, State, or local law; a tax-supported organization; or an Indian tribe or pueblo that controls a commercial service airport. A private entity controlling an airport participating in the Pilot Program for Private Ownership of Airports (49 U.S.C. 47134) may also apply to impose and use a PFC.

The FAA must issue a final decision approving or disapproving a PFC application, in whole or in part. Following the FAA’s full or partial approval of an application to impose a PFC, the public agency must notify air carriers and foreign air carriers required to collect PFCs at its airport(s) of the FAA’s approval, including the approved PFC level and dates of collection. Air carriers collect PFCs from their passengers in accordance with 158.45 or 158.47. Air carriers collecting PFCs are required by section 158.51 to remit the PFC revenue collected, less a prescribed handling fee, to the appropriate public agency on a monthly basis.

Beginning in the year that PFC revenues are first collected by air carriers on behalf of a public agency, such public agencies approved for PFC collection are required by section 158.63 to provide quarterly reports to air carriers collecting PFC revenue for the public agency and the FAA.

The quarterly report is designed to provide the air carriers and the FAA with sufficient information for oversight of PFC revenue. The public agency quarterly report must be provided on or before the last day of the calendar quarter or other period agreed to by the collecting carrier and public agency for which funds were collected.

Similarly, each air carrier collecting PFCs for a public agency must file quarterly reports to the public agency, unless otherwise agreed to by the collecting air carrier and public agency. The air carrier’s quarterly report provides an accounting of funds collected and funds remitted to each public agency.

The air carrier’s quarterly report is required to be filed on or before the last day of the calendar month following the calendar quarter, or other period as agreed to by the collecting carrier and public agency for which funds were collected.

The FAA’s PFC database has been designed to facilitate electronic filing and retrieval of the public agencies’ and the air carriers’ quarterly reports. This will allow both user groups timely access to the other party’s reports and will facilitate standardized record keeping.

The PFC database has been designed with two methods for air carriers to enter their quarterly report information. The first method is a manual data entry wherein the air carrier will select each airport and inputs each data element. The second method is an upload of the quarterly information into the database


### 18256 Federal Register / Vol. 75, No. 68 / Friday, April 9, 2010 / Notices

via a pre-established format through an .xml interface.

Public agencies may enter PFC remittance information into the database by either manual data entry or upload via a pre-established format through an .xml interface. The public agency data entry for projects is limited to manual entry wherein the public agency selects each appropriate project and inputs the data for that project.

The FAA notes that approximately 93 percent of the public agencies approved to collect PFC participate in the PFC database system. Those public agencies and air carriers choosing to use the database will no longer be required to distribute their quarterly reports to any interested party in any other way beginning June 21, 2010.

Issued in Washington, DC, on March 25,

2010. Frank San Martin, Manager, Airports Financial Assistance
Division.

[FR Doc. 2010–8124 Filed 4–8–10; 8:45 am]

**BILLING CODE 4910–13–M**

**DEPARTMENT OF TRANSPORTATION**

**Federal Aviation Administration**

**[Summary Notice No. PE–2010–16]**

**Petition for Exemption; Summary of Petition Received** 

**AGENCY :**  Federal Aviation Administration (FAA), DOT.

**ACTION :**  Notice of petition for exemption received.

**SUMMARY :**  This notice contains a summary of a petition seeking relief from specified requirements of 14 CFR. The purpose of this notice is to improve the public’s awareness of, and participation in, this aspect of FAA’s regulatory activities. Neither publication of this notice nor the inclusion or omission of information in the summary is intended to affect the legal status of the petition or its final disposition.

**DATES :**  Comments on this petition must identify the petition docket number involved and must be received on or before April 29, 2010.

**ADDRESSES :**  You may send comments identified by Docket Number FAA– 2010–0216 using any of the following methods:

• Government-wide rulemaking Web
site: Go to http://www.regulations.gov and follow the instructions for sending your comments electronically.

• Mail: Send comments to the Docket Management Facility; U.S. Department of Transportation, 1200 New Jersey Avenue, SE., West Building Ground Floor, Room W12–140, Washington, DC

20590.

• Fax: Fax comments to the Docket Management Facility at 202–493–2251.

• Hand Delivery: Bring comments to the Docket Management Facility in Room W12–140 of the West Building Ground Floor at 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.

Privacy: We will post all comments we receive, without change, to http:// www.regulations.gov, including any personal information you provide. Using the search function of our docket web site, anyone can find and read the comments received into any of our dockets, including the name of the individual sending the comment (or signing the comment for 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).

Docket: To read background documents or comments received, go to http://www.regulations.gov at any time or to the Docket Management Facility in Room W12–140 of the West Building Ground Floor at 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.

**FOR FURTHER INFORMATION CONTACT :**  Mr. Leslie B. Taylor, phone (816) 329–4134, fax (816) 320–4090, e-mail leslie.b.taylor@faa.gov.

This notice is published pursuant to 14 CFR 11.85.

Issued in Washington, DC, on April 2,

2010. Pamela Hamilton-Powell, Director, Office of Rulemaking. Petition for Exemption

Docket No.: FAA–2010–0216.
Petitioner: Hawker Beechcraft Corporation.

Section of 14 CFR Affected: 14 CFR 23.783(f)(1).

Description of Relief Sought: Hawker Beechcraft Corporation (HBC) requests an exemption from the specific dimensions of the passenger entry door of the Hawker Beechcraft Model 390–2. The door has basic dimensions greater than the minimum required by § 23.783(f)(1). The total area of the model 390–2 cabin door opening minus the area occupied by localized projections is greater than the minimum area required by § 23.783(f)(1); however, the minimum width dimension cannot be met at discrete points due to the protrusions.

[FR Doc. 2010–8128 Filed 4–8–10; 8:45 am]

**BILLING CODE 4910–13–P**

**DEPARTMENT OF TRANSPORTATION**

**Federal Motor Carrier Safety Administration** 

**[Docket No. FMCSA–2004–18898]**

**Withdrawal of Proposed Improvements to the Motor Carrier Safety Status**  **Measurement System (SafeStat) and Implementation of a New Carrier Safety**  **Measurement System (CSMS)**

**AGENCY :**  Federal Motor Carrier Safety Administration (FMCSA), DOT.

**ACTION :**  Notice; request for comments.

**SUMMARY :**  The FMCSA announces that it will replace its Motor Carrier Safety Status Measurement System (SafeStat) with an improved Carrier Safety Measurement System (CSMS) on November 30, 2010. The CSMS has been developed and tested as part of the Agency’s Comprehensive Safety Analysis 2010 (CSA 2010) initiative. Therefore, FMCSA is withdrawing the notice of proposed improvements to SafeStat that was published for public comment on May 3, 2006. SafeStat is an automated algorithm currently used by FMCSA to identify high-risk and other motor carriers for on-site compliance reviews. By implementing the new CSMS algorithm, FMCSA will be able to better identify high-risk motor carriers, make more efficient and effective the Agency’s and its State partners’ allocation of compliance and enforcement resources and provide the motor carrier industry and other safety stakeholders with more comprehensive, informative, and regularly updated safety performance data.

From April 12, 2010 to November 30, 2010, FMCSA will provide individual motor carriers with a preview of their performance data at http:// csa2010.fmcsa.dot.gov. This preview in advance of full implementation on November 30, 2010, will improve safety by effecting early compliance and providing opportunities for motor carriers to become better educated on the new CSMS.

**DATES :**  Submit comments before September 30, 2010.

**ADDRESSES :**  You may submit comments identified by the Docket Number in the heading of this notice by any of the following methods:

• Web site: http:// www.regulations.gov. Follow the