OSWG logo

Hyperlinked Table of Contents in order of discussion (select Ctrl Home to return to this page)

      Welcome and General Discussion

      Awaiting Publication/Closed

201301      D097 Aging Aircraft Programs

201403      E096 Weight and Balance Control Procedures

201214         B342 Extended Operations (ETOPS) with Two Engine Airplanes Under part 121

201315         C070 Airports Authorized for Scheduled Operations

200916         A025 Electronic Record Keeping Systems

201011      C078/079 IFR Lower Than Standard Takeoff Minimums—All Airports                

201110      C055 Alternate Airport IFR Weather Minimums

201421      C052  Straight-in Non-Precision, APV,

              and Category I Precision Approach and Landing Minima—All Airports

201113         B036 Class II Navigation Using Multiple Long-Range Navigation Systems (M-LRNS)

201420      A034 Advanced Qualification Program (AQP)

    

  

      Accommodations        Meeting Information/Attendance          Reference        Directory

  Post-Meeting General Discussion Notes                     AFS Document Production Flow Chart


      Awaiting Publication (moved to closed upon public dissemination)

201302      D485 Aging Airplane Inspection and Records Review

201304      A097, A098, A099 Passenger and Baggage Weight Programs

200505         B343 Performance Based Fuel

201306      B045  Extended Overwater Operations

                 Using a Single LongRange Communication System    

201308       A061 Use of Electronic Flight Bag

201425      C081  Special Non 14 CFR part 97

              Instrument Approach or Departure Procedures

 

 

      Closed (removed from succeeding agendas)

201407       A3xx Ops Spec for Special Cargo (delayed indefinitely)

201309      C059 Category II Instrument Approach and Landing Operations—U.S. Airports

              (delayed indefinitely)

201112      C300  part 97 NDB, NDB/DME, VOR, and VOR/DME       (published)

              Instrument Approach Procedures Using Substitute Means of Navigation                   

201017      A353 ADS-B Operations Outside of U.S. Designated Airspace (Notice published)

201418      B450 Sensitive International Areas (no action required)

201419      B055 North Polar Operations (no action required)

201422      A021 Helicopter Air Ambulance Operations (FAA Brief)

201423    B057 National Parks Air Tour Management Operations Under 14 CFR part 136 (FAA Brief)

201124      B039  Operations within North Atlantic (NAT)

              Minimum Navigation Performance Specifications (MNPS) Airspace (Published)

201426      Order 8400.9            National Safety and Operational Criteria for       (FAA Brief)

                           Runway Selection Plans and Noise Abatement Runway Use Programs

 

 

Domestic Meeting

Tuesday, October 7, 2014

Domestic Industry PreMeeting: 1300-1600, Airlines for America, Washington DC

FAA Pre-Meeting: 1500-1600, Room 833, FAA Headquarters, Washington DC

 

 

Wednesday, October 8, 2014, 0900–1600          (Meeting Attendance)

Airlines for America, Washington DC

Adobe Connect Webinar hosted by Airlines for America—

•  Select this link: http://airlines.adobeconnect.com/room1/.

•  Select Enter as a guest.

•  Type in your full name & click the Enter Room button.

•  After you enter the web conference, a pop up box will appear. Select Dial-out [Receive a call from the meeting]. Enter your phone number in the box below and then click the Join button.

 

 

 

·   Review the OSWG Procedures Guide.

·   Subscribe to the Aviation Safety Draft Documents Open for Comment web site, http://www.faa.gov/aircraft/draft_docs/.

·   Read the current agenda, previous agendas, and meeting summaries on the OSWG Publications web site: http://fsims.faa.gov/PICResults.aspx?mode=Publication&doctype=OSWG.

·   Forward OSWG agenda submissions to respective industry and/or FAA co-chairman a month prior to the quarterly meeting.

 

Accommodations  (effective October 6-10, 2014)

Daily Washington DC federal government lodging/per diem rate: $222.00 / $71.00

Airlines for America has secured corporate rates for several area hotels. To book, guests may call the hotel directly and ask for the Airlines for America rate or book online.

Renaissance Washington DC Downtown  202 898-9000  www.marriott.com/wasrb

999 Ninth Street NW, Washington, DC, near Gallery Place and Chinatown Metro Station

Standard room promotional rate (not including tax): $219.00/night

(use the corporate/promotional rate code 0A4 (zero alpha four))

Comfort Inn Downtown DC/Convention Center  202-682-5300

http://www.comfortinn.com/ires/en-US/html/ArrivalInfo?hotel=DC601&srp=LAFA&pu=no

1201 13th Street NW, Washington, DC, near McPherson Square Metro Station

Standard room promotional rate (not including tax): $170.00/night

 

Directory

Domestic Industry            Andy Newcomer, United Parcel Service

Chairman:                          502 359-5713, anewcomer@ups.com

Domestic Industry            Jim “Wink” Winkelman, Alaska Airlines

Vice-Chairman:                 206 392-6347, jim.winkelman@alaskaair.com

International Industry       Mike Barfoot, Air Canada

Chairman:                          905-676-2176, michael.barfoot@aircanada.ca

International Industry       TBD

Vice-Chairman:                

Domestic FAA                  Steve Kane, AFS-260

Chairman:                          202 604-5564, steve.kane@faa.gov

International FAA            Danuta Pronczuk, AFS-52

Chairwoman:                     202 385-6186, danuta.pronczuk@faa.gov

International FAA            Bryant Welch, AFS-410

Vice-Chairman:                 202 267-8981, bryant.welch@faa.gov

FAA Coordinator             John Bollin, AFS-260

                                          916 202-3608, john.bollin@faa.gov


 

Welcome

Review, revise, and initial sign-in sheet.

Introductions:

Remarks: Industry Chair Andy Newcomer / FAA Chair Steve Kane

Discussion:

·   Navigating the new digital agenda.

·   Purpose of OSWG meeting…; OSWG Procedures Guide

·   Increase use of the Aviation Safety Draft Documents Open for Comment web site.

·   March 2015 WebOPSS training: If no interest, the class will be scheduled for part 129.

·   A4A develop and host OSWG website.

(reference A4A MMEL IG website (login required))

·   Age 65 Rule—ICAO Amendment to remove crew pairing requirement.

·   Next meetings: March/September or March/July/November

·   Industry Vice-Chairman Election.

·   WebOPSS System Update.

·   Economic Authority and Insurance Management (eAIM) System.

·   §121.445 Pilot in command airport qualification: Special areas and airports update.

 

 

Fill out your Stakeholder Survey!

Next Meeting: Domestic/International, Tuesday/Wednesday March 17/18, 2015,

                        Navy Memorial Heritage Center, Washington DC

 

201301             D097 Aging Aircraft Programs

Initial Agenda Date: February 6, 2013                     Date Closed:

FAA Lead: George Padalec, AFS-330, 734 487-7212, george.padalec@faa.gov

Industry Lead: Mike Keller, American Airlines, 918 292-2416, mike.keller@aa.com

Issue Statement: Create a standard for industry and field offices. Provide updated guidance.

Background:

Intended Outcome:

Notes:

·   [8/6/2013 Keller] American Airlines CMO insisting that new aircraft be listed in D097 on delivery…. Issue tabled until next meeting.

·   [2/5/2014 Newcomer] FAA is willing to strengthen the guidance.

·   [5/15/2014 Weiderman] Draft revisions to D097 have been entered into the system for processing; estimated time to completion 6–12 months.

·   [9/15/2014 Weiderman] FAA Lead Frank Weiderman retired. George Padalec has been assigned.

·   [10/8/2014 Padalec] Revising OpSpec and guidance. Modification pending to standardize OpSpec and remove “Free Text”.


201302          D485 Aging Airplane Inspection and Records Review

Initial Agenda Date: February 6, 2013                     Date Closed:

FAA Lead: George Padalec, AFS-330, 734 487-7212, george.padalec@faa.gov

Industry Lead: Mike Keller, American Airlines, 918 292-2416, mike.keller@aa.com

Issue Statement: Clarify interpretation of guidance as to when aircraft is to be added to the OpSpec. Can we decommission?

Background: 14 CFR part 129 applies only to airplanes, not helicopters. If we cannot decommission D485, the part 129 Op Spec should be made into an optional template (airplanes only) and the last four columns should have dropdowns (same as the part 121 template minus the part 135 on-demand template). The 121 template refers to part 129 and has directions within the template.

Intended Outcome: Should there be a job aid for both the part 121 and part 129 templates, and should the directions and references to part 129 in the part 121 templates be deleted?

Notes:

·   [8/6/2013 Miles] AFS300 reviewing possible decommission as the collected data has not been used for the last 7 years. For the interim Mark Lopez, AFS-330,  reviewed the amendment to the part 129 templates which has been initiated. A helicopter is not an airplane and since the rule is for aging airplanes the D485 requirement is being removed for helicopter only operators. Inspector guidance has been drafted to reflect the change. If a policy decision is made to remove D485 for all CFR parts before the draft OpSpec, all documents will be amended to reflect decommission.

·   [2/5/2014 Miles] Domestic and international industry operators have requested that the FAA decommission D485. Nick Petty from executive Jet Management also commented that they are required to have D485, yet D485 says it does not apply to part 135 on-demand operators. International FAA OSWG Chairwoman, Danuta Pronczuk, briefed that for now the FAA will be continuing to process the previously briefed change to D485 for part 129 foreign air carriers. If it is agreed by upper management that the FAA can decommission D485 then instead of making the change, the FAA will decommission D485 for foreign carriers as well.

·   [5/15/2014 Weiderman] Request to archive D485 submitted; estimated time to decommission 6–12 months.

·   [9/15/2014 Kane] FAA Lead Frank Weiderman retired. George Padalec has been assigned.

·   [10/8/2014 Padalec] Awaiting decommission.


201403          E096 Weight and Balance Control Procedures

Initial Agenda Date: June 10, 2014                          Date Closed:

FAA Lead:  George Padalec, AFS-330, 734 487-7212, george.padalec@faa.gov

                     Robert Higgins, AFS-330, 502 753-4283, robert.j.higgins@faa.gov

Industry Lead: Mike Keller, American Airlines, 918 292-2416, mike.keller@aa.com

Issue Statement: 8900.1 Volume 3, Chapter 47 guidance only speaks to weight and CG and has omitted or failed to fully emphasize the requirement in part 25 §25.1583(c) Weight and Loading Distribution.

Background:

Intended Outcome: Add a new table to OpSpec paragraph E-096 titled Load and Control. The table would be authorized for issuance once the CFT has given concurrence to the CMO. The CMO would enter the section/chapter manual where that specific instructions and guidance exist.

Notes:

·   [5/15/2014 Weiderman] The FAA intends to change the title of E096 to reflect its purpose, weighing aircraft. It was determined that the current title—Weight and Balance Control Programs, could mislead a person to think it applies to “operational aspects” of weight and balance.

·   [10/8/2014 Padalec] Changes will be done to other OpSpecs that will affect E096…: The extent has not been determined. The Cargo Focus Team will be a part of this discussion.

    

201304          A097, A098, A099 Passenger and Baggage Weight Programs

Initial Agenda Date: February, 2013                        Date Closed:

FAA Lead: Adam Giraldes, AFS220, 817 3504564, adam.giraldes@faa.gov

Industry Lead: Roy Maxwell, Delta Airlines, 404 715-7231, roy.maxwell@delta.com

                           Chuck Schramek, Delta Air Lines, 424 715-1536, chuck.schramek@delta.com

Issue Statement: Feedback requested: passenger survey weights.

Background: Updates are coming to the weight and balance figures used in AC 12027E Aircraft Weight and Balance Control. Adam and Roy request feedback.

Intended Outcome: Update AC 12027 Aircraft Weight and Balance Control

Notes:

·   [2/6/2013 Schramek] Industry believes it should be a group presentation and not on an airline-by-airline presentation.

·   [2/6/2013 Schramek] Request to Deke Abbott, AFS-220 to make draft AC available for review. Deke indicated the document should be available by the end of March.

·   [2/5/2014 Newcomer] Posted draft AC 120-27F on November 7, 2013, with a comment period closing December 7, 2013. Industry requested an extension of the comment period to 120 days. FAA extended to comment period to January 31, 2014. Comments received by the FAA will take approximately two months to review and up to six months to incorporate.

·   [5/12/2014 Winkelman]: Revised AC pending.

·   [10/8/2014 Kane]: Awaiting publication.

 

200505          B343 Performance Based Fuel (page 1 of 2)

Initial Agenda Date: August 26, 2005                      Date Closed:

FAA Lead:  Gordy Rother, AFS-240, 612 253-4409, gordon.rother@faa.gov

                     Adam Giraldes, AFS220, 817 3504564, adam.giraldes@faa.gov

Industry Lead: Rich Yuknavich, American Airlines, 817 967-5767, rich.yuknavich@aa.com

               Andy Newcomer, UPS, 502 359-5713, anewcomer@ups.com

Issue Statement: Numerous carriers want to be issued this Ops Spec, allowing en-route reserves as low as 5% for that percentage of the total time required to fly from the airport of departure to, and land at, the airport to which it was released. Currently only two part 121 operators, American and United have this OpSpec.

Background: Many international carriers are required to plan for less fuel reserves percentages than U.S. carriers. Many foreign carriers are allowed to use 3% reserves. This has put U.S. carriers at an operating cost disadvantage, even though the FAA-required 10% reserves is only computed on those en-route flight segments that are in Class II airspace. Long flights over Class II airspace experience the largest reserve fuel advantage. A little over ten years ago, the FAA began to level the playing field by granting use of 5% fuel reserves to carriers that could prove their flight planning and weather prediction capabilities provided adequate safety margins. American, United and Continental [ed: merged with United] were issued B343.

Authorization for additional carriers was halted following Congressional interest in one or two widely publicized minimum fuel declarations. However, the long term record of both American and United Airlines is very positive. For example, since May, 2004, American Airlines has flown 767,257 flights using B343 5% planning parameters and has had only 104 of those flights burn into en-route fuel reserves. Most of these “burn-ins” were only a few minutes of fuel, but are reported none the less. Further approvals were also denied based on a planning reliability standard formulated by MITRE that counted fuel percentage of under-burn in the same category as over-burn. In the case of FedEx, over-burns were due to contingency added fuel to account for frequent MD-11 tail-fuel-transfer failures. When normal transfers occurred, fuel consumption was much less than planned.

More recently, further approvals are being delayed in anticipation of ICAO publication of international fuel reserve guidelines. There is a desire to ensure that U.S. policies harmonize with ICAO standards. FAA is working toward a Performance Based fuel reserves model similar to the draft ICAO Annex 6. FAA has requested that carriers review and comment on Annex 6 (draft) through IATA or ATA. Once the new Annex 6 is settles/issued, the theory is that B343 should be resurrected. A new FAA Advisory Circular is being drafted by the FAA.

(continued on next page)

200505          B343 Performance Based Fuel (page 2 of 2)

Intended Outcome: Provide for performance based fuel reserves for U.S. air carriers sooner than later.

Notes:

·   [9/26/2005 Johnson] Jim handed out proposed changes to B343. One of the proposals is to allow a combination of both the 5% and Re-dispatch deviations. The FAA was receptive to some of the proposed requests and will review them as appropriate.

·   [4/17/2012 Seabright] Steve Kuhar, FedEx, expressed frustration at linking additional approval to a slow ICAO process. John Cowan, United, and Rich Yuknavich, American, asked for and received confirmation that their carrier track records using five percent authority has been excellent.

·   [7/17/2012 Seabright] Steve Kuhar, FedEx stated that the majority of the industry believes that the FAA should not have issued the B343 authorization to just a few carriers, but instead to all eligible. If more carriers were issued B343 a much larger performance database would have been accumulated. FAA contends that any operator may still apply for issuance, and if the requirements are satisfied, will eventually be issued. In the interim, the OpSpec disparity exists.

·   [2/5/2013 Shramek] ICAO 6 is out and FAA is working on new Advisory Circular for Performance Based fuel loads. Close B343 from agenda and add new item of Performance Based Fuel Loads.

·   [2/5/2014 Newcomer] Drafting guidance for new OpSpec, will provide OSWG with copy.

·   [2/5/2014 Newcomer] Performance based fuel will align with SARPs and ICAO on fuel (10% reserve to as low as 5% reserve). Not just computing, but a “system” including time of day, route, where you fly, your aircraft, airport arrival rate, etc.

·   [2/5/2014 Newcomer] Provide data collection criteria and how to share with CMO.

·   [2/5/2014 Newcomer] Parallels ICAO Annex 6, part 1 (SARP, known fuel vs. unplanned).

·   [2/5/2014 Newcomer] Harmonization effort.

·   [2/5/2014 Newcomer] Approvals at CMO and not at headquarters.

·   [5/30/2014 Rother] The FAA is slowly working with the proof-of-concept carrier (UAL). We may have something more substantial this fall.

·   [10/8/2014 Kane] Awaiting publication.

 

201306          B045 Extended Overwater Operations

            Using a Single LongRange Communication System (awaiting publication)

Initial Agenda Date: August 6, 2013                        Date Closed:

FAA Lead: Gordy Rother, AFS-240, 612 253-4409, gordon.rother@faa.gov

Industry Lead: Grant LeClaire, Southwest Airlines, 404 559-3645, grant.leclaire@airtran.com

Issue Statement: Create a standard for industry and field offices. Provide updated guidance.

Background: Removes the time limit that is in the current paragraph and the required letters of agreement from KZNY, KZJX, KZMA and KZHO. Proposed is a 30-day look back of HF radio reliability. If there are two failures within the 30 days, aircraft would be limited to one leg in the WATRS airspace unless the aircraft has an operational Sat voice system. The paragraph is in coordination at Headquarters. Anticipated release date is fall of 2014.

Intended Outcome: Under review and request for carrier participation.

Notes:

·   [9/7/2013 Schramek] Question of 90-day may be excessive. Industry working on a compromise. Goal is for policy within a month.

·   [2/5/2014 Newcomer] “We are close”—next 2/3 week complete internal coordination. Will post for comments soon.

·   [2/5/2014 Newcomer] 30-day look-back.

·   [2/5/2014 Newcomer] SAT Voice is a mitigation.

·  [2/5/2014 Newcomer] New language addresses difference between the MRSAT and Iridium.

·  [5/30/2014 Rother] B045 is currently at AFS-140. The ETA is mid-July then it goes to formal coordination. If all goes well the group can expect it on the street by September.

·  [10/8/2014 Kane] Awaiting publication pending AFS-140 review.


 

201407     A3xx Ops Spec for Special Cargo (closed)

Initial Agenda Date: June 10, 2014                          Date Closed: October 8, 2014

FAA Lead:  Steve Moates, AFS-220, 202 267-4147, stephen.moates@faa.gov

                     George Padalec, AFS-330, 734 487-7212, george.padalec@faa.gov

                     Robert Higgins, AFS-330, 502 753-4283, robert.j.higgins@faa.gov

Industry Lead: Steve Kuhar, Federal Express, 901 224-5339, sjkuhar@fedex.com

                           Andy Newcomer, UPS, 502 359-5713, anewcomer@ups.com

Issue Statement: Resolve the issue of “special cargo”.

Background: As part of the aftermath of the April 2013 National Air Cargo B747 accident in Bagram, Afghanistan, the FAA formed a team tasked to address the issue of special cargo. The team’s original tasking was to review the weight and balance manuals of every operator. The next step is a concurrence to carry “Special Cargo” authorized by issuance of an A3xx OpSpec.

Intended Outcome: Create a 300-level Op Spec addressing the carriage of “Special Cargo”.

Notes:

·   [6/10/2014 Kane] Notice 8900.262—Review of Weight and Balance Control Programs Including Special Cargo Operations was issued on May 6, 2014.

·   [10/8/2014 Kane] Issued removed from agenda pending internal FAA review.

 

201308          A061 Use of Electronic Flight Bag (awaiting publication)

Initial Agenda Date: August 6, 2013                        Date Closed:

FAA Lead: Brian Hint, AFS430, 202 267-8415, brian.hint@faa.gov

Industry Lead: Jim Winkelman, Alaska Airlines, 206 392-6347, jim.winkelman@alaskaair.com

Issue Statement: Request updated guidance.

Background: Reference AC 120-76C Guidelines for the Certification, Airworthiness, and Operational Use of Electronic Flight Bags.

Intended Outcome:

Notes:

·   [2/5/2014 Newcomer] On ship position, moving map is now Type B (FAA Order and Advisory Circular)

·   [2/5/2014 Newcomer] Ops Spec will add language to reduce AC120-76C to harmonize with EASA.

·   [2/5/2014 Newcomer] Install or portable with Type A or Type B; eliminate classes. Cancel Type C EFB user forum in Memphis in May.

·   [2/5/2014 Newcomer] Eliminate all the software versions in the table as long as the POI validates the revision method.

·   [2/5/2014 Newcomer] Table will be in drop down format.

·   [5/8/2014 Hint] An interim change will be developed for the OpSpec language to:

(1)  Clarify when an OpSpec for EFB functions are required.

(2)  Make it clear that AMMD with own-ship is a Type B Software application.

(3)  Allow for an easier transition for the next version (which will eliminate Type C software applications and require OpSpecs only for Type B EFB Software applications).

·   [5/8/2014 Hint] Tables for Operator/POI entry will be updated to include a drop-down menu (based upon FAR Part) to standardize table input.

·   [5/8/2014 Hint] Eliminate all the software versions in the table as long as the POI validates the revision method.

·   [5/8/2014 Hint] Discuss long term vision for EFB OpSpec requirements.

·   [10/8/2014 Kane] Awaiting publication.


201309          C059 Category II Instrument Approach and Landing Operations—

            U.S. Airports (closed)

Initial Agenda Date: February 6, 2013                     Date Closed: October 8, 2014

FAA Lead: Bryant Welch, AFS-410, 202 267-8981, bryant.welch@faa.gov

Industry Lead: Andy Newcomer, UPS, 502 359-5713, anewcomer@ups.com

Issue Statement: Controlling RVR needs to be clarified: Mid RVR 0 or rollout RVR 0 was never acceptable.

Background: In the amended OpSpec it will specify that all RVRs are controlling vs. just touchdown. Also specified minimum values for mid RVR 600 and rollout RVR 300 for CAT II (1200/600/300). The OpSpec was also rearranged, first step toward combining with C060. For CAT II currently touchdown zone is controlling, and mid and rollout is advisory. Changing to all available RVRs are controlling. Specifying minimum values for rollout so you cannot land with RVR 200 in rollout. Result of looking at several company manuals that rollout RVR 0 is OK.

Intended Outcome:

Notes:

·   [8/6/2013 Welch] Vetted through the DCB, out for formal coordination. Following this change AFS-400 plans on combining C059 with C060.

·   [2/5/2014 Welch] Bryant reported that inspector guidance required for the issuance of a foreign air carrier’s OpSpecs, is delayed and expected to be out in the next few months. The OpSpec template has been issued. The compliance date will be 120 days from the date of the international inspector guidance being published. Bryant emphasized that if all three RVRs are available, they are controlling. Comment from the floor was that the N/A for mid and roll out in the table next the touchdown RVR 1600 row was confusing. Several members requested an amendment to the OpSpec. Bryant confirmed that the way N/A in that row (mid and rollout) was supposed to be interpreted for was: “…if reported then 1600 or above, if not reported then 1600 touchdown is all that is required.” Bryant took the IOU to make the requested editorial for both the foreign air carrier and U.S. domestic templates.

·   [10/8/2014 Newcomer/Kane] Changes to C059 are delayed and will not be forthcoming for the foreseeable future. The co-chairs elected to close the issue and reopen when the FAA has more information to present to the OSWG.

 

201110                                                                      C055 Alternate Airport IFR Weather Minimums (page 1 of 2)

Initial Agenda Date: August 2, 2011                        Date Closed:

FAA Lead: Cathy Graham, AFS-470, 202 267-8842, catherine.m.graham@faa.gov

Industry Lead: Jim Winkelman, Alaska Airlines, 206 392-6347, jim.winkelman@alaskaair.com

Issue Statement: Confirmation that this applies to all alternates or limited to destination alternates.

Background: Some carriers interpret AC 120-42B Extended Operations (ETOPS and Polar Operations) paragraph 303.C.(5) to mean that Ops Spec C052 authorization for RNAV/GPS approaches constitutes authorization for use of the provision in that paragraph for use of GPS based en-route alternate minimums:

303.C.(5) ETOPS Alternate Minima. A particular airport may be considered to be an ETOPS alternate for flight planning and dispatch purposes, if the latest available forecast weather conditions from the earliest time of landing to the latest time of landing at that airport, equals or exceeds the criteria detailed in the following table. Because OpSpecs alternate weather minima standards apply to all alternates, the following criteria is recommended for a typical certificate holder’s OpSpecs. An individual certificate holder’s OpSpecs must reflect current requirements (§121.625). Although no consideration for the use of GPS/RNAV approaches is presented here, operators may request to receive this authorization through the FAA. This authorization would be reflected in the operator’s OpSpecs. Appropriate ETOPS alternate minima for such operations will be determined by the Director, Flight Standards Service. The airport of departure (takeoff) and the destination airport (unless used concurrently as an ETOPS alternate) are not required to meet the weather minima for ETOPS alternates as these airports are subject to other regulations (e.g., §§ 121.617, 121.621, and 121.623).

OpSpec/MSpec/LOA C055, Alternate Airport IFR Weather Minimums was published to authorize certificate holders/program managers/operators to derive alternate airport instrument flight rules (IFR) weather minimums in those cases that require an alternate airport. Notice N8900.218 Alternate Airport IFR Weather Minimums (5/30/13) describes changes that allow operators with unaugmented Global Positioning System (GPS) navigation systems to plan for use of GPS-based instrument approach procedures (IAP) at destination or alternate airports (but not both locations) in the U.S. National Airspace System (NAS).

(continued on next page)

 

201110                                                                      C055 Alternate Airport IFR Weather Minimums (page 2 of 2)

Background (continued): Currently, selectable text is being added to C055 in order to allow part 121 and 135 operators to file for GPS based IAP at an ETOPS alternate, under certain conditions.  Until publication of this change, operators may request the use of GPS-based IAP minima at ETOPS alternate airports through non-standard text. Applications for this temporary non-standard text should be made to AFS-200 through the guidance contained in FAA Order 8900.1, Volume 3, Chapter 18, Section 2, paragraphs 3-712 and 3-713.

Intended Outcome: Allowance for use of RNAV/GPS approach minima at en-route alternate airports.

Notes:

·   [10/16/2012 Seabright] Steve Moates, AFS 220, and John Swigart, AFS-470 stated that those carriers who interpreted AC 120-42B as allowing Ops Spec C052 issuance as blanket authorization to use RNAV/GPS approach minimums for ETOPS en-route alternate suitability is wrong—Special, specific HQ FAA approval, is required. Such approval will likely not be entertained until the larger issues which are subject to the ongoing MITRE Corporation study, are resolved.

John related that there are GPS satellite coverage issues in various parts of the world such as the Pacific and South America that make a blanket allowance for worldwide RNAV/GPS approach minimums utilization without limitations and special provisions an imprudent course of action.

John further stated, if a carrier could make a case for a special allowance, such as Continental did for its Micronesian Island operations, then some relief may be possible. In such cases, RAIM predictions and close monitoring of inflight performance would be expected.

·   [8/7/2013 Schramek] RNAV GPS approaches are not to be used for an ETOPS alternate unless non-standard language is added to C055. A Notice will be published for the procedures to obtain the non-standard language. This will be used until the template can be revised.

·   [2/5/2014 Newcomer] Should have received a memo from AFS-400 for ETOPS alternates.

·   [2/5/2014 Newcomer] 700 meters may be used in lieu of 800 meters.

·   [9/4/2014 Graham] Updating the template to add selectable text to allow part 121/135 operators to file for a GPS based IAP at an ETOPS alternate is awaiting publication of a change to guidance and a Notice.

·   [10/8/2014 Kane] Notice and 8900.1 guidance awaiting signature for formal coordination.


(page 1 of 3)

 

201011C078/C079 IFR Lower Than Standard Takeoff Minimums—All Airports 

Initial Agenda Date: April 20, 2010                         Date Closed:

FAA Lead:  Bryant Welch, AFS-410, 202 267-8981, bryant.welch@faa.gov

                     Chris Hope AFS-410, 202 267-8976, chris.hope@faa.gov

                     Danuta Pronczuk AFS-52, 202 385-6186, danuta.pronczuk@faa.gov

Industry Lead:   Chuck Schramek, Delta Airlines, 404 715-1536, chuck.schramek@delta.com

                             Bryan Miles, Emirates, 971 4 708 4264, bmiles@emirates.com

Issue Statement: Delete the requirement for using a Head-Up Display (HUD) for lower than standard takeoff minimums RVR 400/400/400.

Background: EASA and ICAO both have provisions for RVR 400/400/400 (125 meters) takeoff without a HUD. [ed: This issue was generated by previous International OSWG discussions regarding Part 129 OpSpecs C056 IFR Takeoff Minimums—Airplanes. For programming purposes in WebOPSS, lower-than-standard takeoff minimums were removed from part 121 OpSpec C056 and part 135 OpSpec C057 and moved to new paragraphs C078/C079.]

Intended Outcome: Revise lower than standard takeoff minimums for both part 121 and part 135 operations.

Notes:

·   [4/20/2010 Pronczuk] International OSWG new business. [ed: Revise Part 129 OpSpec C056 and decommission Part 129 OpSpec C057]

·   [11/3/2010 Pronczuk] Continuing to research applicable Standards for Terminal Instrument Procedures (TERPS) found in FAA orders and 14 CFR regulations: §97.20(a), Order 8260.3, and §91.177.

·   [11/2/2011 Pronczuk] Questions from the OSWG:

·   Is it takeoff run or should it be takeoff roll?

·   Do the visible centerline lights extend for the entire runway length? 

·   Operative runway edge lights at night for the 1000/1000/1000, InFO 07009 recommends them, should the OpSpec as well?

·   Is it certificated seats or actual?

·   The small aircraft, 100 hour PIC requirement was questioned.

 

201011C078/C079 IFR Lower Than Standard Takeoff Minimums—All Airports  (page 2 of 3)

Notes:

·   [4/18/2012 Pronczuk] AFS-50, International Programs and Policy and AFS-400, Flight Technologies and Procedures have reviewed the issues brought forth at the November 2011 meeting. Answers:

·   Is it takeoff run or should it be takeoff roll? Takeoff roll.

·   Do the visible centerline lights extend for the entire runway length? The pilot needs to see enough centerline lights to maintain centerline for the required runway length for the aircraft (the greater of accelerate-stop or accelerate-go and normal takeoff to 35 feet).

·   Operative runway edge lights at night for the 1000/1000/1000, InFO 07009 recommends them, should the OpSpec as well? Changed to serviceable HIRL or CL (current OpSpecs uses the term “operative”). Reason: HIRL could be operational but not at the required level of see them—Airports use the not-serviceable terminology. (It was noted that if the lights were NOTAMed, the terminology used would be “not-in-service”. A request was made to defice “serviceable” in 8900.1 guidance and through a job-aid.

·   Is it certificated seats or actual? Certificated seats.

·   The small aircraft, 100-hour PIC requirement was questioned. Delete the 100-hour PIC requirement.

·   [4/18/2012 Pronczuk] An updated draft Part 129 OpSpec C056 was posted for public comment. Comments are due by July 11, 2012. AFS-50 and AFS-410 are still looking at adding RVR 300/300/300.

·   [10/17/2012 Miles] Chris Hope, AFS-410, reviewed the OpSpec changes: new minima, terminology, etc. since last meeting added 300/300/300 with HUD (same limitations as those imposed on US domestic air carriers). Inspector guidance has been pre-coordinated between AFS-50 and AFS-400. John Conlon, British Airways, also reviewed the revised draft and it looked good from the industry perspective. Look for the updated draft to be posted for comment in the next couple of weeks.

·   [7/9/2013 Welch] Notice 8900.224 published. Added 500/500/500 and 300/300/300 tables with glance view of lowest authorized by type.

·   [8/7/2013 Welch] Since last meeting one additional selectable was added within the table: 700/700/700. (200 meters = 700 feet).

·   [8/7/2013 Miles] Chuck Schramek, Domestic Industry Chairman, asked if the FAA permits foreign air carriers to takeoff with 400/400/400 without a HUD, will the domestic industry be permitted as well. Bryant confirmed yes. More details expected at the next OSWG.

(continued on next page)

 

201011C078/C079 IFR Lower Than Standard Takeoff Minimums—All Airports  (page 3 of 3)

Notes:

·   [8/7/2013 Miles] Post 2013 OSWG update: The 2009 job aid that no longer applies has been removed and the new job aid and help text in subparagraph d (the references within it) has been corrected.

·   [2/5/2014 Newcomer] EASA confirmed that establishment of lower take-off minima was based on a simulator study performed on a KLM B747. Bryant advised that the FAA has requested a copy of the study and is still waiting. Without a copy of the study the only way the FAA would consider the proposal would be to conduct its own simulator study. For the FAA to consider conducting its own study there would have to be proof of a need. U.S. and foreign air carriers who feel that there is such a need are requested to track to which airports and how many takeoffs at those airports they could not do because the weather was less than RVR 500. This analysis should be completed prior to the next joint session (scheduled for March, 2015). Bryan Miles, International OSWG industry chair, commented that EASA only authorized Category A, B, C, for 400 takeoff without HUD. Bryant commented that this will be easier to review once we have a copy of the study.

·   [2/5/2014 Newcomer] Post meeting addendum: Takeoff visibility is limited to 1sm for 2-engine aircraft (regulatory reference §91.175(f)). Question to FAA: Can the visibility restriction be reduced to ½sm if the foreign CAA authorizes? Question to industry: How many commercial operators operate with one engine? Is there a need? What are the mitigations? (New technology/more reliable engines….)

·   [5/7/2014 Welch] Should say “400 without HUD for everybody”, but only if EASA test is found and accepted by the FAA. So far we have nothing from EASA. This should probably be closed and only reopened if test data found.

·   [10/8/2014 Welch] The EASA study was obtained and the issue remains open. Reference the April 1986 Flight Simulator Experiments Concerning Takeoff Visibility Minima.


201112                                                                                                          C300 part 97 NDB, NDB/DME, VOR, and VOR/DME                                       (closed)

            Instrument Approach Procedures Using Substitute Means of Navigation

Initial Agenda Date: August 2, 2011                        Date Closed: October 8, 2014

FAA Lead: Kel Christianson, AFS-470, 202 267-8838, kel.christianson@faa.gov

Industry Lead: Jim Winkelman, Alaska Airlines, 206 392-6347, jim.winkelman@alaskaair.com

                           Rich Yuknavich, American Airlines, 817 967-5767, rich.yuknavich@aa.com

Issue Statement: Suitable NAVAID substitution authorizations are needed by operators in certain circumstances or areas of the world.

Background: C300 was developed to provide standard methodology for authorizing NAVAID sub-procedures for approach operations. The current template does not meet the needs of all operators or provide the latitude necessary for certain circumstances. There are no plans to make any immediate changes to the Ops Spec; however, 470 would entertain submission of non standard language for special cases. Carriers, especially those without Ops Spec C300, should make maximum use of the provisions outlined in AC 90-107 for RNAV substitution. Depending on the final analysis of a MITRE study, AFS-470 may first allow use of C300 for alternate approaches.

Intended Outcome: Provide a mechanism to authorize use of NAVAID substitution or mitigation procedures that meet the needs of both Industry and FAA, especially for alternate airport minimums.

Notes:

·   [2/5/2014 Newcomer] Take away WAAS requirement?

·   [2/5/2014 Newcomer] At AFS-1 for signature—will publish soon.

·   [6/23/2014 Christianson] OpSpec C300 published. The WAAS restriction has been removed. Subparagraph c(11) has been changed to allow use of C300 for alternate airport planning. Reissue C300 if the certificate holder wishes to use C300 for alternate airport planning. Certificate holders must be issued C055, and follow all limitations and provisions within C055 to use C300 for planning purposes at alternate airports using specific RNAV equipment. HQ concurrence is not required for reissuing C300 templates unless Table 1, Aircraft and Equipment Authorization, is amended. See Notice 8900.266 for further information.

·   [10/8/2014 Newcomer/Kane] Notice published, issued is closed.

 

201113          B036 Class II Navigation Using Multiple Long-Range Navigation Systems

            (M-LRNS) (page 1 of 2)

Initial Agenda Date: August 2, 2011                        Date Closed:

FAA Lead: Madison Walton, AFS-470, 202-267-8850, madison.walton@faa.gov

Industry Lead: Ellen Birmingham, UAL, 872 825-5193, ellen.birmingham@united.com

                           Steve Kuhar, Federal Express, 901 224-5339, sjkuhar@fedex.com

Issue Statement: Industry requests updated guidance.

Background: Industry representatives contend that the requirement for deliberate fixing procedures have been made obsolescent by modern multi-sensor FMS navigation systems that use constant DME-DME or GPS and DME-DME fixing to update the FMS present position. Furthermore, industry contends that deliberate flyover position fixing or radar fixing is much less accurate than automatic position updating and may increase the possibility of position errors during position fixing if an unintentional position update occurs.

Intended Outcome: Clarify the provision to specify that it is referring to non GPS equipped aircraft as follows:

“Prior to entering any airspace requiring the use of a non GPS based long-range navigation system, the aircraft position shall be accurately fixed using airways navigation facilities or ATC radar. After exiting this airspace, the aircraft position shall be accurately fixed and the long-range navigation system error shall be determined and logged in accordance with the operator's approved procedures.”

Some industry representatives expressed a desire to include multisensory DME-DME updating in the above verbiage. The FAA has no initial objections to this minor addition.

Notes:

·   [1/18/2012 Seabright] Rich Yuknavich, American Airlines, proposed to modify draft language concerning navigation accuracy checks to accommodate aircraft with automatic position updating (DME/DME or GPS). This would cover aircraft without GPS installed and would also cover aircraft with inoperative GPS.

·   [7/17/2012 Walton] Madison presented draft OpSpec B036/B054 proposals. As soon as it is available, Paul Lepine, AFS-260, will make Notice 8900.B036 available for industry review.

·   [10/16/2012 Walton] At the insistence of carriers with all GPS equipage, the coast-in/coast-out Navigation Accuracy Check verbiage was changed to eliminate the provision for “DMD/DME automatic position updating”. Ops Spec template tables will also include RNP 4 and RNP 10 time limits.

(continued on next page)

201113          B036 Class II Navigation Using Multiple Long-Range Navigation Systems

            (M-LRNS) (page 2 of 2)

Notes:

·    [2/5/2013 Walton] MSpec for part 91 and part 125 to be revised to address single, long range nav. FAA to provide guidance and possible up-date to paragraph that multi sensor FMS positioning using GPS or DME is satisfactory for determining navigation system accuracy.

·   [12/4/2013 Kane] Notice 8900.246 OpSpec/MSpec/LOA B036 Class II Navigation Using Multiple Long-Range Navigation Systems (M-LRNS) published.

·   [6/10/2014 Walton] Awaiting FAA AGC legal interpretation.

 

 

201214          B342 Extended Operations (ETOPS) with Two Engine Airplanes Under part 121   (page 1 of 2)

Initial Agenda Date: October 16, 2012                     Date Closed:

FAA Lead:  Theo Kessaris, AFS240, 202 267-4561, theodora.kessaris@faa.gov

                     Steve Moates, AFS-220, 202 267-4147, stephen.moates@faa.gov

Industry Lead: Andy Newcomer, UPS, 502 359-5713, anewcomer@ups.com

Issue Statement: The FAA is proposing to revise Op Spec B342 to remove the requirement to list airplane registration numbers and ETOPS alternate airports. Airplane registration numbers are already listed in D086.

Background: AFS-220/260 is reevaluating the need to list aircraft registration numbers in B342. D086 already contains this information and discrepancies exist between the aircraft numbers listed in D086 and those listed in B342. With respect to ETOPS Alternate Airports, the FAA has realized that the B342 OpSpec is somewhat inaccurate by listing ETOPS Alternate Airports. The FAA believes that listing those airports in a HQ approval OpSpec serves no purpose to the FAA or industry.

Intended Outcome: Update Op Spec B342 Table 1: Remove the column for Airplane Registration Number and delete Table 2.

Notes:

·   [10/16/2012 Kessaris] Theo agreed to remove the aircraft table, and asked if any carriers objected to removal of the ETOPS alternate airport listing. Her idea is to move ETOPS alternates to OpSpec C070 by assigning the applicable airports the code letter “E”. Industry agreement was unanimous.

·   [10/16/2012 Schramek] Ongoing discussion…; concern of the alphabet soup. Per Theo, no it won’t—Language of regular, provisional, or fueling will transfer from B342 to C070. Operators will not have to designate an airport as an “E” when it is already an “R”.

·   [10/16/2012 Schramek] Industry is waiting on a legal interp. Reason for delay is due to other priorities.

·   [2/5/2013 Newcomer] Industry would like the new guidance to stay within the ETOPS subject matter not include other associated items like that of crew times or FIR boundary. Industry would also like to keep the alternate listing as an optional separate list.

·   [2/5/2014 Newcomer] Theo will go to AFS-220 to see if they can take on the aircraft table.

(continued on next page)


(page 2 of 2)

 

201214          B342 Extended Operations (ETOPS) with Two Engine Airplanes Under part 121

Notes:

·  [5/13/2014 Kessaris] AFS-220 will remove the column for Airplane Registration Number. The Op Spec template and guidance will be revised.

·   [10/8/2014 Kessaris] Theo provided a draft of the new B342 template. The associated guidance is still in the process of being updated. Target for publication of the new template and all of the associated guidance is no later than June 2015.


·   

201315          C070 Airports Authorized for Scheduled Operations

Initial Agenda Date: February 5, 2013                     Date Closed:

FAA Lead: Theo Kessaris, AFS240, 202 267-4561, theodora.kessaris@faa.gov

Industry Lead: Doug Snow, Federal Express, 901-397-8228, douglas.snow@fedex.com

Issue Statement: Adequate Airports for ETOPS would be entered in C070 under a new category of “E” for “Adequate Airport for ETOPS”. C070 would then be revised for the addition of the new “E” category airport.

Background: The B342 OpSpec is somewhat inaccurate by listing ETOPS Alternate Airports. The FAA believes that listing those airports in a HQ approval OpSpec serves no purpose to the FAA or industry.

Intended Outcome: Update OpSpec C070: Allow the selection of “E” airports and make the OpSpec applicable for part 121 supplemental and part 135 certificate holders.

Notes:

·   [8/6/2013 Schramek] Ongoing discussion…; concern of the alphabet soup. Per Theo, no it won’t—Language of regular, provisional, or fueling will transfer from B342 to C070. Operators will not have to designate an airport as an “E” when it is already an “R”.

·   [8/6/2013 Schramek] Industry is waiting on a legal interp. Reason for delay is due to other priorities.

·   [8/6/2013 Schramek] Supplemental Carriers will list ETOPS adequate airports in C070.

·   [2/5/2014 Newcomer] Theo will go to AFS-220 to see if they can take on the aircraft table.

·   [5/16/2014 Newcomer] American Airlines has issues with listing multiple aircraft types authorized into a regular airport. They are requesting a possible concept of provisional aircraft.

·  [10/8/2014 Kessaris] Theo provided a copy of the draft C070 template. The associated guidance for C070 is finished. The template is tied to the B342 Extended Operations (ETOPS) with Two Engine Airplanes project. Estimated publication date for both C070/B342 is no later than June, 2015.

200916          A025 Electronic Record Keeping Systems (page 1 of 3)

Initial Agenda Date: July 21, 2009                           Date Closed:

FAA Lead: Theo Kessaris, AFS240, 202 267-4561, theodora.kessaris@faa.gov

Industry Lead: Casey Seabright, Delta Air Lines, 402 715-1536, charles.seabright@delta.com

                           Jim Winkelman, Alaska Airlines, 206 392-6347, jim.winkelman@alaskaair.com

Issue Statement: FAA & Industry are using A025 as a catchall for authorizations that may not be appropriate for this paragraph or may be appropriate but are listed individually versus categorically.

Background: An audit of A025 shows significant variability in the items placed in this paragraph. The impetus for more specific guidance is increasing with the expanding adoption of cockpit Electronic Flight Bags (EFBs) and the corresponding transition from paper manuals to purely digital format manuals. The direction of some POIs and PMIs to list every digital document individually versus by class of documents is becoming more burdensome as the number of digital document continues to multiply.

Intended Outcome: Maintain A025 as a repository for electronic record keeping and an optional storehouse for electronic signatures and electronic manuals. Amend A025 to include tables for specific approvals such as flight planning systems, training records repositories, and categories of electronic/digital manuals.

Notes:

·   [1/19/2011 Kessaris] On hold…. When work on this is ready to begin again, industry would like to get a subgroup together to help write the new OpSpec. Once AGC is able to provide their assistance, the FAA will attempt to establish a workgroup similar to the one that worked on B044 to help write OpSpec A0xx which will address electronic systems that calculate things such as fuel as a means of compliance with several regulations. Guidance on the “clean up” of A025 will be introduced after the creation of A0xx.

·   [1/18/2012 Kessaris] On hold pending further research, reflection and cogitation. There are currently numerous overlapping guidance documents. No easy fix. “In for a dime in for a dollar”. Theo is looking for general suggestions or multiple Industry leads.

·   [4/17/2012 Seabright] Steve Kuhar, FEDEX, suggested a separate OpSpec for electronic manuals or allowing a general authorization for electronic manuals without requiring a specific OpSpec listing for each new manual. Eventually all manuals will only be electronic. Casey volunteered to work with Jim Winkleman, Alaska Airlines, and Theo Kessaris, AFS-260, to draft guidance proposals.

(continued on next page)

200916          A025 Electronic Record Keeping Systems (page 2 of 3)

Notes:

·   [7/17/2012 Kessaris] Theo voiced concern that there are no resources on the FAA side to work the issue. She solicited help from industry if there is a desire to make progress on this project. Industry representatives seemed amenable to forming a sub-group to draft proposed changes to the OpSpec template, 8900.1 guidance and possibly a revision to AC120-78 Acceptance and Use of Electronic Signatures, Electronic Recordkeeping Systems, and Electronic Manuals.

·   [7/17/2012 Kessaris] Theo voiced concern that there are no resources on the FAA side to work the issue. She solicited help from industry if there is a desire to make progress on this project. Industry representatives seemed amenable to forming a sub-group to draft proposed changes to the OpSpec template, 8900.1 guidance and possibly a revision to AC120-78 Acceptance and Use of Electronic Signatures, Electronic Recordkeeping Systems, and Electronic Manuals.

·   [7/17/2012 Seabright] The impetus for more specific guidance is increasing with the expanding adoption of cockpit Electronic Flight Bags (EFBs) with increasing transition from paper manuals to purely digital format manuals. The direction of some POIs and PMIs to list every digital document individually versus by class of documents is becoming more burdensome as the number of digital document continues to multiply. The opportunity for an FAA/OSWG conference did not materialize.

·   [2/5/2013 Schramek] No movement, only maintenance requirement change for part 91. Industry would like to see this paragraph back to original purpose. Item is currently on hold.

·   [9/7/2013 Schramek] The issue is ongoing. If there are interested parties within industry who desire to submit a proposal, FAA would take that into account. For now an A025 rewrite is on hold due to other FAA priorities.

·   [2/5/2014 Newcomer] Current Status: On hold until AC120-78 is published.

·   [2/5/2014 Newcomer] Theo will post changes for us to comment on sometime in the future. No draft or template yet.

·   [2/5/2014 Newcomer] Focus on Manuals, signatures and records.

·   [2/5/2014 Newcomer] Build a template similar to the 145 template.

·   [2/5/2014 Newcomer] AC120-78 will be updated. Comments have not been incorporated.

·   [2/5/2014 Newcomer] Wants to explore each system per system regulations, what constitutes an acceptable electronic signature, what is an acceptable electronic manual.

(continued on next page)

200916          A025 Electronic Record Keeping Systems (page 3 of 3)

Notes:

·   [6/10/2014 Kessaris] AC 120-76C Guidelines for the Certification, Airworthiness, and Operational Use of Electronic Flight Bags, has been posted with new policy/definition on manuals, records and electronic signatures.

·   [6/10/2014 Kessaris] No more “free text”, but will have a drop down for manuals, type of records and electronic signature.

·   [10/8/2014 Kessaris] Theo provided a draft A025 template for part 121. The template will apply only to those signatures, records and manuals required by regulation. All of the templates and associated guidance have been written; however, the Advisory Circular is currently on hold pending additional internal review.

201017          A353 ADS-B Operations Outside of U.S. Designated Airspace (closed)

Initial Agenda Date: April 20, 2010                         Date Closed: October 8, 2014

FAA Lead:  Dennis Mills, AFS220, 202 267-4552, dennis.mills@faa.gov

                     Roger Sultan, AFS-430, 202-267-8922, roger.sultan@faa.gov

Industry Lead: Andy Newcomer, UPS, 502 359-5713, anewcomer@ups.com

Issue Statement:

Background:

Intended Outcome: List authorized countries in paragraph B050 instead of A353, Table 1,

4th column. Specific aircraft tail numbers will remain in A353.

Notes:

·   [8/6/2013 Schramek] New streamlined guidance will be coming out in the near future. Word has it that Viet Nam and Taiwan will be requiring ADSB Out soon.

·   [2/5/2014 Newcomer] Remove the table/authorization if your equipment is appropriate.

·   [2/5/2014 Newcomer] Will check with AFS-400 to see if they can move it to local vs. headquarters approval.

·   [5/20/2014 Mills] A353 is undergoing a major rewrite. Suggestions made by industry are being incorporated; authorization by region and/or local level, areas of authorization stated in B050, and a simplified method of obtaining authorization.

·   [7/17/2014 Mills] Notice 8900.269 was issued to replace OpSpec A353 with A153. The new OpSpec is designated for approval at the CHDO/Flight Standards District Office (FSDO)/PI level. Changes will be incorporated into pending revisions of AC 90-114 Automatic Dependent Surveillance‑Broadcast (ADS-B) Operations, and FAA Order 8900.1, Volume 3, Chapter 18, Section 3, Part A Operations Specifications—General.

·   [9/25/2014 Kane] The AC and 8900.1 guidance formal coordination comments have been resolved. The documents are in AFS-140 final review.

·   [10/8/2014 Newcomer/Kane] Notice 8900.269 is published; issue is closed.

201418          B450 Sensitive International Areas (closed)

Initial Agenda Date: June 10, 2014                          Date Closed: October 8, 2014

FAA Lead:  Deke Abbott, AFS-220, 202 267-8266, deke.abbott@faa.gov

Industry Lead: Andy Newcomer, UPS, 502 359-5713, anewcomer@ups.com

Issue Statement: Data required for entry into the paragraph is not listed in the DOT website

Background: Operators issued B050 for areas/countries registered in the FAA Air Traffic Prohibitions, Restrictions, and Notices website as having Travel Alerts, are required to be listed in B450. These countries are not found in The DOT Bureau of Consular Affairs Alerts and Warnings website. For example, Madagascar, Mozambique, Nepal, and Turkey are enumerated in the B450 pull downs with no travel alert recorded on the DOT site. It appears that the DOT website is not updated.

Intended Outcome: Update the DOT website. Unless there is a discussion to sunset B450, no change to the paragraph is requested.

Notes:                                                                                                               

·   [9/15/2014 Kane] Requests for B450 data are made throughout the year by other federal agencies. B450 will not be sunset.

·   [10/8/2014 Newcomer/Kane] No further action is required. The issue is closed.

 

 201419         B055 North Polar Operations (closed)

Initial Agenda Date: June 10, 2014                          Date Closed: October 8, 2014

FAA Lead:  Adam Giraldes, AFS220, 817 3504564, adam.giraldes@faa.gov

Industry Lead: Rich Yuknavich, American Airlines, 817 967-5767, rich.yuknavich@aa.com

Issue Statement: The template column for alternate airports is limited to a single aircraft entry.

Background: Unable to add more than one aircraft for each polar alternate, operators are adding a second alternate airport row as a workaround.

Intended Outcome: Revise the B055 alternate airports template column to allow more than one aircraft entry.

Notes:

·   [10/8/2014 Kane] Clerical issue requiring request made through AFS chain of command. American agreed to initiate request on behalf of all carriers holding the OpSpec.

·   [10/8/2014 Newcomer/Kane] No further action is required, the issue is closed.

201420          A034 Advanced Qualification Program (AQP)

Initial Agenda Date: October 8, 2014                       Date Closed:

FAA Lead:  Rob Burke, AFS 280, 202 267-8262, robert.burke@faa.gov

Industry Lead: Ellen Birmingham, UAL, 872 825-5193, ellen.birmingham@united.com

Issue Statement: This OpSpec is in dire need of amendment.

Background: There is no consideration for Flight Crew, Inflight, and/or Dispatch AQPs—For example, Table 1 specifies initial and final approval dates for Indoctrination; but no place to add this for the various work groups. Table 2 requires aircraft M/M/S, which is too detailed even for pilot training, but again, does not accommodate Dispatchers or Flight Attendants. In addition, Table 2 lists Instructors and Evaluators by aircraft M/M/S. The IE curriculum may or may not be fleet specific, but there are IE Indoc, IE Qualification and IE Continuing Qualification curricula separate from the pilot Indoc, Qual, and CQ.

Intended Outcome: Revise and update the OpSpec.

Notes:

·   [10/8/2014 Burke] Rob gave the group a look at proposed changes to the TSpecs. AFS-210 is looking to combine information into a single specification. Industry would prefer smaller pieces of information in several specs…; publish the OpSpec or reference the training manual. The draft Training Specification was exclusive to the current OSWG briefing and not for public dissemination. This document will not be included in the post-meeting notes.

 

201421          C052 Straight-in Non-Precision, APV,               (FAA Brief)

                                and Category I Precision Approach and Landing Minima—All Airports

Initial Agenda Date: October 8, 2014                       Date Closed:

FAA Lead:  Cathy Graham, AFS-470, 202 267-8842, catherine.m.graham@faa.gov

Industry Lead: Not Applicable

Issue Statement: OpSpec/MSpec/LOA C052 is not required for Part 91 operators. NBAA and other organizations have received inquiries from foreign states asking for proof that the part 91 operators have approval to fly to LPV minima on GNSS based approaches.

Background: AFS400 and AFS800 are receiving inquiries from part 91 operators requesting documentation to show foreign states their authorization to fly LPV minima. The FAA is still investigating the details of how many operators this might encompass and which states require documentation. In the meantime Flight Standards is developing Order 8900.1 guidance to accompany an optional LOA for part 91.

Intended Outcome: Develop an optional LOA template available for part 91 operators who plan to fly LPV minima in foreign states. The LOA will not be required to fly LPV minima in the United States.

Notes:

·   [10/8/2014 Graham] AFS-200, -400, and -800 are working on draft 8900.1 guidance and an LOA template.

 

201422          A021 Helicopter Air Ambulance Operations (closed)

Initial Agenda Date: October 8, 2014                       Date Closed: October 8, 2014

FAA Lead:  Andy Pierce, AFS-250, 202 267-8238, andy.pierce@faa.gov

Industry Lead: Not Required

Issue Statement: OpSpec A021 Helicopter Emergency Medical Services (HEMS, now Helicopter Air Ambulance, HAA) will be revised to implement congressional mandated HAA flight operations data collection:  Reference Notice 8900.A021 OpSpec A021 Helicopter Air Ambulance Operations and Advisory Circular 135.14B Helicopter Air Ambulance.

Background: HAA flight operations data collection is a statutory requirement imposed by Title 49 USC 44731. Industry input was solicited and incorporated into development of the report.

Intended Outcome: HAA Operators will submit annually using a template provided by the FAA. No requirements affecting operational safety have been added.

Notes:

·   [10/8/2014 Pierce] Issue is on fast track for publication and presented to the OSWG for information only. Reference guidance: Draft Order 8900.1 Volume 3 Chapter 18 Section 3 OpSpec A021.

·   [10/8/2014 Pierce] HAA Data Collection for Congressional Mandate OpSpec A021 Power Point presentation.

·   [10/8/2014 Newcomer/Kane] FAA brief. Issue closed.

  

201423          B057 National Parks Air Tour Management Operations Under 14 CFR part 136  (Closed)

Initial Agenda Date: October 8, 2014                       Date Closed: October 8, 2014

FAA Lead:  Andy Pierce, AFS-250, 202 267-8238, andy.pierce@faa.gov

Industry Lead: Not Required

Issue Statement: All B057 OpSpec and LOA templates for operators conducting air tour operations under parts 91, 121, 121/135, and 135 will be revised to add an option for voluntary agreements and resulting, new Operating Authority, conditions, and limitations. A congressional mandated Commercial Air Tour flight operations data collection requirement will also be added. Reference Notice 8900.xxx OpSpec/LOA B057 National Parks Air Tour Management Operations Under 14 CFR part 136.

Background: The Federal Aviation Modernization and Reauthorization Act of 2012 (Public Law 2012-95 Section 501(e) Overflights of National Parks) requires a Voluntary Agreement (VA) to be considered as an available alternative to an Air Tour Management Plan (ATMP). A VA establishes a set of conditions and limitations on the annual number of air tours conducted, their flight path through a National Park Service (NPS) unit, time of day authorized, etc. A VA requires less rigor in the environmental assessment that is required for an ATMP. This same statute requires implementation of Commercial Air Tour reporting for all NPS units.

Intended Outcome: B057 records and maintains the assigned Initial Operating Authority for an operator in a particular NPS unit, or lists the ATMP or VA (when implemented) which specifies conditions and limitations governing conduct of Commercial Air Tours within the NPS unit and a maximum number of air tour operations per year. This OpSpec/LOA also requires the Operator to submit periodic Commercial Air Tour Flight Operations Activity Reports.

Notes:

·   [10/8/2014 Pierce] Issue is on fast track for publication and presented to the OSWG for information only.

·   [10/8/2014 Pierce] National Park Service Data Collection for Congressional Mandate OpSpec B057 Power Point presentation.

·   [10/8/2014 Pierce] Reference corresponding National Park Service Data Collection for Congressional Mandate OpSpec B049 (Grand Canyon National Park).

·   [10/8/2014 Newcomer/Kane] FAA brief. Issue closed.

  

201124             B039        Operations within North Atlantic (NAT)

                                    Minimum Navigation Performance Specifications (MNPS) Airspace

Initial Agenda Date: November 2, 2011                   Date Closed: October 8, 2014

FAA Lead:  Madison Walton, AFS-470, 202-267-8850, madison.walton@faa.gov

                     Kevin Kelley, AFS-470, 202-267-8854, kevin.c.kelley@faa.gov

Industry Lead: Not Required

Issue Statement: North Atlantic MNPS to PBN transition will cause a revision to B039.

Background: The NATSPG has concluded that NAT MNPS airspace will transition to NAT PBN airspace. Beginning January 1, 2015, operators seeking authorization to operate in NAT MNPS airspace will be required to meet the navigation specifications of RNAV 10 or RNP 4. Operators already authorized MNPS are grandfathered until January 1, 2020. (ICAO Doc. 7030, NAT Chapter 4, Para. 4.1.1.5.1.5)

Intended Outcome: Revise applicable OpSpec/MSpec/LOA for U.S. operators to comply with this requirement. Transition to PBN will support improved air navigation services, e.g. reduced lateral and longitudinal separation minima.

Notes:

·   [8/7/2013 Pronczuk] OpSpec revision, Notice, and 8900.1 inspector guidance survived Document Control Board vetting and was forwarded to AFS-140 for formatting and formal coordination.

·   [2/5/2014 Pronczuk] The OpSpec and associated inspector guidance were signed off for publication. The new template is expected to be available for issuance in the March/April, 2014 time frame.

·   [10/8/2014 Kane] Published: Kevin Kelly gave a Power Point presentation: NAT MNPS Change to OpSpec B039 Version 5, October 7, 2014. Issue is closed.

 

201425             C081        Special Non 14 CFR part 97

                                    Instrument Approach or Departure Procedures  (FAA Brief)

Initial Agenda Date: October 8, 2014                       Date Closed:

FAA Lead:  Kel Christianson, AFS-470, 202 267-8838, kel.christianson@faa.gov

Industry Lead: Not Required

Issue Statement: Revise C081 to include RVFPs and STARs. Update process for inspectors to follow in order to provide carriers with proper guidance for developing, submitting and publishing special instrument procedures.

Background: (Previous OSWG issue closed in 2013.) A public instrument flight procedure (IFP) is one that has been promulgated under 14 CFR Part 97. Often times Special instrument flight procedures that have been authorized for multiple users have been referred to as “Public Specials”. In actuality, these are not “public” procedures although some in the industry continue to refer to them as such. The majority of those “Special” IFPs that have been authorized for multiple users are maintained by the Aeronautical Products Division of Mission Support Services, formerly known as AeroNav Services or the National Flight Procedures Office. The Aeronautical Products Division enters into a reimbursable agreement to develop/maintain those Special IFPs used by a single operator. The issue concerning the appropriateness of seeking reimbursement (from operators) for Special IFPs that have been authorized for multiple users has been referred to Legal.

Intended Outcome: Determine who is responsible for “Specials” or move them to the public domain. Move inspector guidance from 8900.1 V4 to V3. Provide operators with one OpSpec to list special airports and procedures authorized. Update templates with new tables and information. Provide description of other OpSpecs that may be required.

Notes:

·   [10/8/2014 Christianson] Issue update presented to the OSWG for information only.

·   [10/8/2014 Kane] Awaiting publication.


201426             Order 8400.9                                                       National Safety and Operational Criteria for  

                             Runway Selection Plans and

                             Noise Abatement Runway Use Programs  (page 1 of 2) (Closed)

Initial Agenda Date: October 8, 2014                       Date Closed: October 8, 2014

FAA Lead:  John Blair, AFS-410, 202-267-8986, john.blair@faa.gov

Industry Lead: Not Required

Issue Statement: Revise Order 8400.9 National Safety and Operational Criteria for Runway Selection Plans and Noise Abatement Runway Use Program to include most towered airports and particularly, those towered airports that operate in less than optimal wind conditions for various “operationally advantageous” reasons.

Background: Order 8400.9 is being revised (and a supporting Advisory Circular created) that will affect all part 139 towered airports in the NAS and require them to document their runway selection plans based on wind parameters (for airport reconfiguration purposes) as determined by a local Runway Selection Safety Team (RSST). A key component for the successful completion of the RSST plan is industry (user) involvement at each location. Quality user (pilot) input within the RSST will result in safer operations by reducing the number unplanned airport reconfigurations prompted by pilot refusal of a particular runway assignment (or missed approaches, missed high speed exits, long rollouts, etc.) and reduce the number of occasions that pilots are put in the position of having to refuse a runway assignment. The end goal of the RSST is to develop and document a plan that integrates a high level of safety with each location’s operational realities, therefore, allowing for a more proactive approach to managing airport configuration changes.

 

201426             Order 8400.9                                                       National Safety and Operational Criteria for 

                             Runway Selection Plans and

                             Noise Abatement Runway Use Programs  (page 2 of 2) (Closed)

Intended Outcome:

Positive:

·   Increased safety.

·   Reduced number of times pilots are put in the uncomfortable position of having to refuse a runway assignment.

·   Agreed upon and documented crosswind and tailwind limits allowing for more proactive management of airport configuration changes.

·   Users having input into the formulation of plans.

·   Dependent on outcome, industry input at the RSST could potentially reduce operator costs (taxi time, capacity…).

Negative:

·   Industry will need to expend resources to provide representation at the RSST.

·   For cost justification, in addition to safety, industry input could potentially increase operator costs (taxi time, capacity…).

Notes:

·   [9/23/2014 Blair] Issue presented to the OSWG for information only.

·   [10/8/2014 Blair] Order 8900.9 Power Point Presentation.

·   [10/8/2014 Blair] Advisory Circular due in mid 2015.

·   [10/8/2014 Blair] Order 8900.9. Exclusive to current OSWG briefing, not for public dissemination. This document will not be included in the post-meeting notes.

·   [10/8/2014 Newcomer/Kane] FAA brief. Issue closed.

 

 

October 2014 OSWG Meeting Discussion Notes

·   [John Bollin] John assisted those experiencing problems navigating the new digital agenda.

·   [John Bollin] New linked item: the meeting attendance sheet…; check your information and reply if correction is required.

·   [John Bollin] How come it takes so long to publish a document? The recently revised AFS System Level Process for Production of Policy, Guidance, and Information Documents (Document Flow Chart) has been added to the agenda.

·   [Mark Lopez] Airlines for America is beta testing the A4A Operations Council OpSpecs Working Group website. The portal requires A4A authorization and is password protected. As the site matures, meeting agendas (past, and present), documents open for public comment, and general information will be posted.

·   [Andy Newcomer] Andy Newcomer’s last day in office. Jim Winkelman is the new Domestic Industry Chairman. Ellen Birmingham, UAL, was elected Domestic Industry Vice-Chairwoman.

·   [Andy Newcomer] The single-day OSWG meeting schedule worked: in by 0900, out by 1500 with an hour for lunch. The membership agreed to conduct three meetings in 2015. The previously scheduled March 17/18 joint international/domestic session, and domestic only sessions scheduled for July 22 and November 4. Domestic only pre-meetings will be held in the morning of March 17 and the afternoon of July 21 and November 3. A4A will host the July meeting and NBAA will host the November meeting.

·   [Andy Newcomer] The joint international/domestic OSWG meeting is scheduled for Tuesday/Wednesday, March 17/18, 2015 at the Navy Memorial Heritage Center, Washington DC. Submit issues for discussion to an OSWG FAA or industry co-chair. The agenda will be distributed 3-4 weeks prior to the meeting.

·   [Steve Kane] Steve offered details of the no fee, WebOPSS training scheduled for the March, 2015 joint international/domestic meeting. A team of qualified FAA instructors has been formed. Two one-day, 6-hour sessions will be offered. The Tuesday session is reserved for international air carrier/operator registration. The Wednesday course will be earmarked for domestic registrants. Danuta Pronczuk, International FAA Chairwoman, informed the group of the intense interest from the international community. Vacant seats for the domestic session on Wednesday will be offered to international registrants on a wait list. All enrollees will require FAA Principle Inspector authorization for attendance and eventual access to WebOPSS and assigned digital signature. Detailed information and a registration process will be provided at a later date.

October 2014 OSWG Meeting Discussion Notes (continued)

·   [Steve Kane] Updating the changing ICAO age 60 pairing requirement: AFS-200 will publish a policy statement (Notice) on or soon after the effective date of the new ICAO standard, announcing that the FAA will no longer enforce §121.383(c)(2) because it is contrary to 49 U.S.C. Section 44729. The agency will initiate rulemaking to conform §121.383 to the statute. Outside US airspace, carriers are required to operate according to the rules of the member state. Certificate holders will need to check with each DGAC and ensure they are not contrary to the rules of that country.

·   [Monica Grusche] A substantial WebOPSS update is in the works and should be released in about a month or so. The release updates the backend platform for WebOPSS as well as incorporating 40+ fixes and enhancements.

·   [Monica Grusche] AFS-260 is also overhauling the system that manages Air Taxi Registrations and Amendments and aircraft accident liability insurance. The new Economic Authority and Insurance Management (eAIM) System is scheduled to be released in Spring 2015.

·   [Steve Kane] §121.445 Pilot in command airport qualification: Special areas and airports update: No changes to date.

 

June 2014 OSWG Meeting Discussion Notes

·   [John Bollin] John assisted those experiencing problems navigating the new digital agenda.

·   [John Bollin] The latest (October 2011) OSWG Procedures Guide has been uploaded to FSIMS. John is working on a revision incorporating current policies and procedures.

·   [John Bollin] AFS-260 is exploring the use of the AFS Draft Documents Open for Comment web site for public comment to upcoming and ongoing OSWG issues.

·   [Steve Kane] Steve recommended combining the two half-day domestic only sessions into a single, one-day meeting…: All AFS divisions would be represented, facilitating greater participation and interaction with FAA SMEs during the session. Industry agreed to a joint meeting on Wednesday, October 8, 2014, in the A4A conference room. The industry only and FAA only pre-meetings will be held Tuesday afternoon.

·   [Andy Newcomer] No change will be made to the joint international/domestic OSWG calendar—Meetings will continue to be scheduled for three sessions spanning two days. After coordinating calendar dates with international chair persons Danuta Pronczuk and Mike Barfoot, and confirming location with Steve Kane, the next joint international/domestic meeting will be held on Tuesday/Wednesday, March 17/18, 2015, at the Navy Memorial Heritage Center, Washington DC.

June 2014 OSWG Meeting Discussion Notes (continued)

·   [Steve Kane] No fee, WebOPSS training will be scheduled for the March, 2015 joint international/domestic meeting. Two one-day, 6-hour sessions will be offered. Detailed information and a registration process will be provided at a later date.

·   [Steve Kane] Responding to a question regarding ICAO changing the age 60 pairing requirements, Danuta Pronczuk did a little great deal of research and forwarded her findings to Steve Kane. Steve spoke with FAA rulemaking (ARM)—They are aware of the changes taking place. Direct to final rule making is possible and there is a good chance the domestic rule can be amended in time to coincide with the effective date of the ICAO changes. AFS-200 will be the POC for any rulemaking effort.

·   [Kel Christianson] Responding to a question regarding a MITRE study on cold weather altimetry, AFS-470 is drafting text and guidance for cold weather altimeter procedures at airports identified in the MITRE study. Airports will be listed as a Notice to Airman “Digital Product”. Industry recommended that the FAA develop policy and train controllers.

·   [Andy Newcomer] …will chair the OSWG one last time in October. Jim Winkelman will start his 2-year tour next year. The 2015/16 Vice-Chairman position remains open.

·   [Monica Grusche] Digital Certificate Service updated: Subscribers will now receive prompts to renew 30, 15, 5 and 1 day before expiration with the new signature provider.

·   [Monica Grusche] The Maintain Operator Data–Aircraft menu has been expanded to display more than 10 aircraft.

·   [Monica Grusche] If a Maintain Operator Data item is blank, it will load “NA” (not applicable) into a document instead of “No system data.”

·   [Monica Grusche] The 8900.1 guidance for Commercial Aviation Safety Team (CAST) Safety Enhancement (SE) Surveys under new Part S has been released. A total of 24 CAST SE surveys are expected to be released in groups of 6 with the first 6 and an InFO published on June 4, 2014. Survey response is voluntary.

·   [Monica Grusche] AFS-260 is developing a “work around” for batch processing and eliminating dropped signatures when you batch process.

·   [Paul Lepine] Working with several contractors, AFS-260 will establish a web-based operations approval entry portal and a web-based work package to accommodate the needs of multiple FAA Lines of Business. Expected release date: September 2015. Reference Paul’s NavLean Recommendation 21 presentation.

·   [Steve Kane] §121.445 Pilot in command airport qualification: Special areas and airports update: New Quito, Ecuador International Airport (Tababela) was added.

 

Significant Historical OSWG Meeting Discussion Notes

·   [February 2014, Monica Gusche] FAA transitioned to a new digital certificate provider in June, 2013. Industry users can acquire or renew a digital signature certificate from the agency’s DCS Home Page at https://dcs.faa.gov/. This site also includes instructions on how to acquire or renew such certificates. The FAA is unable to support signatures renewed with previous digital signature providers. Industry has inquired about adding additional credit card forms of payment for purchasing digital certificates through DCS, such as American Express and Discover. The FAA and the DCS contractor are investigating whether the agency can absorb the fees within the current digital certificate cost structure.

·   [February 2014, Monica Gusche] Obtaining a digital certificate does not determine access to WebOPSS.  Industry must approach their Principle Inspector to request access to WebOPSS. The PI must (1) vouch for the user having been adequately trained to use the system, (2) sponsor the user for external access to the FAA network, and (3) request a WebOPSS account for the user.  Digital certificates should not be purchased until and unless access to WebOPSS has first been established.

·   [February 2014, Monica Gusche] WebOPSS transitioned its operations and maintenance support to a new contractor in May, 2013. The agency and the contractor are making significant progress working through bug fixes and cleanup issues with WebOPSS. The FAA is in the process of packaging the latest of these items in an application update which should be released in the next couple months. One of the enhancements in the release package will be the ability to display more aircraft at a time on the Maintain Operator Data—Aircraft area of WebOPSS.  The default will still be 10, but there will be options to change to 25, 50, or 100 aircraft at a time.

·   [August 2013, Monica Gusche] The contract with Team Askin, the agency’s digital service provider, expired. The FAA has signed with Lockheed Martin for WebOPSS maintenance and Digital Certificate Service (DCS). The new DCS website is https://dcs.faa.gov/. The price remains the same: $30.50 per digital signature for the first issuance (good for a year). Foreign air carriers and foreign persons who are not a U.S. resident may complete and submit a notarized proof of identity form. The form and instructions are available on the DCS website. Operators who obtained their digital signature from Team Askin can still use their digital signature until it expires before renewing with the new DCS.

 

AFS System Level Process for Production of Policy, Guidance, and Information DocumentsAFS 002-103 Process Flow Map

Page 1 of 2 Hyperlinked References (select Ctrl End to return to references page 2 of 2)

FAA Order 8900.1 Flight Standards Information Management System (FSIMS)

FAA Order 8900.1 Volume 3 Chapter 18 Operations Specifications

Section 1 Operations Specifications: Background Information

Section 2 Automated Operations Safety System

Section 3 Part A Operations Specifications—General

Section 4 Part B Operations Specifications—En route Authorizations and Limitations

Section 5 Part C Operations Specifications—Airplane Terminal Instrument Procedures and

                                                                        Airport Authorizations

Section 6 Parts D and E—Maintenance MSpecs/OpSpecs/LODAs

Section 7 Part H—Helicopter Terminal Instrument Procedures and

                              Airport Authorizations and Limitations

Section 11 Parts A, B, and D Operations Specifications for part 145 Repair Stations

FAA Order 8900.1 Volume 12 Chapter 2 Foreign Air Carriers Operating to the U.S. and Foreign Operators of U.S.-Registered Aircraft Engaged in Common Carriage Outside the U.S.

Section 2 Part 129 Operations Specifications Overview and Issuance

Section 3 Part 129 Part A Operations Specifications

Section 4 Part 129 Part B Operations Specifications— En route Authorizations and
                                                                                       Limitations

Section 5 Part 129 Part C Operations Specifications— Airplane Terminal Instrument
                                                                                       Procedures and
                                                                                       Airport Authorizations

Section 6 Part 129 Part D Operations Specifications—         Aircraft Maintenance

Section 7 Part 129 Part H—Helicopter Terminal Instrument Procedures and

                                             Airport Authorizations and Limitations

 

Page 2 of 2 Hyperlinked References (select Ctrl End to return to this page)

Title 14 Code of Federal Regulations (14 CFR) Aeronautics and Space

part 91 General Operating Rules

part 91 §91K Fractional Ownership Operations

part 119  Certification: Air Carriers and Commercial Operators

part 121  Operating Requirements: Domestic, Flag, and Supplemental Operations

part 125  Certification and Operations: Airplanes Having a Seating Capacity of 20 or

               More Passengers or a Maximum Payload Capacity of 6,000 Pounds or

               More; and Rules Governing Persons on Board Such Aircraft

part 129  Operations: Foreign Air Carriers and Foreign Operators of

               U.S.-Registered Aircraft Engaged in Common Carriage

part 135  Operating Requirements: Commuter and On Demand Operations and

               Rules Governing Persons On Board Such Aircraft

FAA Employee Directory

Aviation Safety Draft Documents Open for Comment

Regulatory and Guidance Library

WebOPSS Field User Guide

WebOPSS