FAA/Aviation Industry Agenda for
OpSpec Working Group (OSWG) 2011-04

November 1-2, 2011

Tuesday, November 1:  1:00 PM - 5:00 PM

Wednesday, November 2: 9:00 AM – NOON – Joint Session

Wednesday, November 2: 1:00 PM – 5:00 PM – International Session


Hosted by FAA

Heritage Center (Navy Memorial)

Washington , DC


Tuesday, November 1, 2011—9:00 am – noon Domestic Industry Premeeting



Meeting Schedule:

Domestic Sessions

January 17 - 18, 2012

OSWG 2011-01

Washington D.C.

Domestic, Joint, and International Sessions

April 17 – 18, 2012

OSWG 2011-02

Washington , D.C.

Domestic Sessions

July 17-18, 2012

OSWG 2011-03

Washington , D.C.  


Chairpersons:       U.S. Domestic (Part 121, and 135)

                              Steve Kuhar, FEDEX, Industry Chair

                              Casey Seabright, Delta, Industry Vice Chair

                              Bob Davis, AFS-260, FAA Chair


AFS Air Transportation Division, AFS-200, Manager: John Duncan


International (Part 129)

Brian Miles, Emirates, Industry Chair

David Oliver, Qantas Airways Limited, Industry Vice Chair

Danuta Pronczuk, AFS-52, FAA Chair

Mike Frank, AFS-52, FAA Vice Chair


AFS International Programs and Policy Division Manager: John Barbagallo 


IFO/IFU/SEA FSDO Representatives to the Part 129 OSWG :   David Krueger (DFW IFO), Dave Henthorn and Bryan Ashley (LAX IFO), Rolfe Dinwoodie (ROC and ALB IFU), Herbert H. Herzog III,  W. Scott Schweizer and Patrick Crowley (ANC IFU), J.J. (MIA IFO), Robert L. Jaffe (NY IFO), and David May (SEA FSDO)


IATA Representative:   Mrs. Rommy Ulloa for Jeffrey T. Miller


Meeting Location: Heritage Center (Navy Memorial)

701 Pennsylvania Avenue, NW

Washington, DC 2004

                               (phone: 202-737-2300)


Table of Contents


U.S. Domestic Session                 Joint Session                          International Session

Part 121, 135, etc.                                          Part 121, 129, 135 etc.                           Part 129

(Operators for whom the U.S. is               (Foreign air carriers, persons,          (Foreign air carriers and persons)

The State of the Operator)                         & Operators for whom the U.S. is

                                                                        The State of the Operator)


 1.   Convene                                         

1.   Convene                                      

1.   Convene                                              

 2.   Chairman’s Discussion              

 2.  Recognition                                

 2.  OpSpecs B034 and B035                

 3.   OpSpec A010                                

 3.  Stakeholder Survey                   

 3.  OpSpec B039                                     

 4.   OpSpec C050                                

 4.  WebOPSS Update                     

 4.  OpSpec B046                                     

 5.   OpSpec C081                                

 5.  ICAO Register of AOCs            

 5.  Part 129 Rulemaking                        

 6.   OpSpec C073                                

 6.  OpSpec A029                             

 6.  OpSpec  A001                                    

 7.   OpSpec A353                                

 7.  OpSpecs A003/C091                

 7.  OpSpecs  A006 & A007                    

 8.   OpSpec S400                                

 8.  OpSpec D301                             

 8.  OpSpec A008                                     

 9.   OpSpec  A025                               

 9.  OpSpec C063                             

 9.  OpSpecs A036 & A040                     

10.  OpSpec B343                                

10. OpSpec C055                            

10. OpSpec D085                                    

11.  OpSpec C300                               

11. OpSpec C060 (Cascading Authorizations)                                  

11. OpSpec C080                                    

12.  OpSpec C355                               

12. OpSpec C060 (RVR Requirements)                                 

12.  OpSpecs C056 & C057                  

13.  OpSpec A317                                

13. OpSpec C060 (Limitations/SF Lights)                                                

13.  OpSpecs C075 & C076                  

14.  OpSpec D105                               

14. OpSpec D095                                                               

14.  OpSpecs B051 & B056                   

15.  OpSpecs B036/B054                   

15. D485

15.  OpSpec B031                                    

16.  Closing                                           

16. Closing

16.  OpSpec A028                                    



17.  Closing



































U.S. Domestic Session

Tuesday, November 1st  

1:00 pm – 5:00 pm


  1.  Convene .

Opening remarks .



2.  Chairperson’s discussion.


Goals for 2011

Re-format agenda and meeting minutes.



Update format

• Ensure there is an Industry and FAA lead for each topic



Clean up format

• Move away from the extensive discussion within the body of the minutes

• Create separate documents for agenda and minutes


Finalize the updated OSWG Procedures Guide

Clean up Roster


Bob Davis – Opening remarks.



3.  A010: Aviation Weather


FAA Lead: Theo Kessaris, AFS-260 – Leo Hollis, AFS-220

Industry Lead:


Issue Statement:


This paragraph to be revised will add a table for Adverse Weather Systems. The

revision will be applicable to part 121 only. Also, the 8900.1 guidance will be re-written

to match the paragraph.




Status:   On Hold with FAA Legal

The Draft template has been removed from the draft documents website due to the

group’s request to submit the template and guidance together. Therefore, the FAA will

post A010 when the final changes to the template are made and the guidance is

completed. The group will be given the standard amount of time to comment on the

changes at that time.



4.  C050: Special Pilot-in-Command Qualification Airports.


Standing Agenda Item:


Status:   Continuing.



5.  Special Non 14 CFR Part 97 Instrument Approach or Departure



FAA Lead: John Swigart, AFS-470

Industry Lead: Jim Winkleman


Issue Statement:

Who is responsible for maintenance, upkeep and the costs associated with Special

flight Procedures (sometimes referred to as “Public Specials”).



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 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.


Status:  Open.  AFS-470 is waiting for an interpretation from Legal.

Update to be provided by John Swigart.



6.  C073: IFR Approach Procedures Using Vertical Navigation


FAA Lead: Kel Christianson AFS-470

Industry Lead: Joe Devito


Issue Statement:

The certificate holder is authorized to conduct the instrument approach procedures

other than ILS, MLS, or GPS landing system (GLS) utilizing a visibility and a decision

altitude/(height) [DA(H)] equal to the published visibility and minimum descent altitude

(MDA) using the following aircraft and procedures as specified in this operations




Based on near-term safety benefits of using a continuously defined vertical path to the

runway, and a long-term goal of simplifying approach training and qualification

standards, users have indicated their intent to begin additional use of VNAV capability

for instrument approaches.


Intended Outcome:

Request update from Industry Lead


Status: Open.  (Update to be provided by Joe Devito).



7.  A353: Automatic Dependent Surveillance – Broadcast (ADS-B)


FAA Lead: Dennis Mills AFS-220

Industry Lead: Mike Davis


Issue Statement:

Development of an authorization for operations through the Hudson Bay area.



This paragraph was originally created in response to the request from the Canadian

authorities. Template should be designed to include ADS-B IN and ADS-B OUT.

System to include a “RAIM”-like prediction tool.


Intended Outcome:


Status:  Open.  (AC for ADS-B operations is in final coordination).



8.  Safety Enhancement S400: CAST Safety Enhancements.


FAA Lead: Keeton Zachary, Greg Michael

Industry Lead: Steve Bush


Standing Agenda Item:


Issue statement:

S400 is a data collection tool intended to gather critical information about the voluntary

implementation of Safety Enhancements.



These Safety Enhancements were developed by the joint government and industry

Commercial Aviation Safety Team (CAST) over the last several years.

The intent of this paragraph is to gather information on Safety Enhancement

implementations only.

Principal Inspectors should not make safety determinations from the information

provided on S400.

Intended Outcome:

1. Educate Safety Inspectors that completing S400 is voluntary and that no

compliance determinations should be made as a result of S400.

2. Modify WebOPSS so that information in S400 is de-identified upon entry.

3. Ensure information in S400 is FOIA protected

4. Eliminate the need for participation by the Principal Inspector (signature)

Note: Discuss beta test program and June 20th letter to AFS-260.


Status:   Monitor



9.  A025: Electronic Record Keeping Systems.


FAA Lead: Theo Kessaris AFS-260

Industry Lead: Casey Seabright, Jim Winkelman


Issue Statement:

A025 has become a dumping ground for many authorizations that may not be

appropriate for this paragraph .



An audit of operator’s A025 show significant variability in the items placed in this



Intended Outcome:

Transform A025 from being a dumping ground and keep it only as a depository for

primarily electronic record keeping plus 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 other electronic/software applications.


Status:  On Hold

Note: Industry would like to form a subgroup to help write the new OpSpec.



10.  B343: Fuel Reserves for Flag and Supplemental Operations.


FAA Lead: Gordy Rother, MSP-FSDO, Leo Hollis, AFS-220, Dave Burnham, UAL CMO

Industry Lead(s): Steve Kuhar


Issue Statement:

A short statement summarizing the core issue is requested from the Industry lead.



OpSpec B343 is a nonstandard authorization that has been granted to only a few

international air carriers. This is a performance-based authorization using fuel burn

data and statistical analysis within certain criteria as justification. Although the airlines

are not experiencing any problems or concerns, a single (minor) low fuel event caused

the FAA some concern. Hence, for now the FAA will not consider allowing less than a

5% fuel reserve and, until recently, was not granting any new approvals.


Intended Outcome:

Summary of goals requested from the Industry Lead.


Status:  On Hold

Discuss whether this should be removed from agenda.



11.  C300: Part 97 NDB, NDB/DME, VOR, and VOR/DME Instrument

Approach Procedures Using Substitute Means of Navigation


FAA Lead: John Swigart, AFS-470

Industry Lead: Jim Winkleman, Rich Yuknavitch


Issue Statement:

Suitable Navaid substitution authorizations are needed in by operators in certain

circumstances or areas of the world.



C300 was developed to provide standard methodology for authorizing navaid sub

procedure for approach operations. The current template does not necessarily meet the

needs of all operators or provide the latitude necessary for certain circumstances.


Intended Outcome:

Provide a mechanism to authorize navaid sub procedures that meets the needs of both

Industry and FAA.


Status:  Open.  Update from AFS-470, Jim Winkleman, Rich Yuknavitch.

Status of Mitre study.



12.  C355. Exemption to §121.619 for Domestic Destination Alternate

Airport Requirements



Industry Lead: John Cowan


Issue Statement:

C355 contains the following provision:

“The intended destination airport must have at least one operational CAT I ILS

approach with minima of at least 200 feet and RVR 2000 that is available for use if


1. It appears the intent is that the minima for the approach should be no greater than

200 feet. In other words, an ILS with a 200 foot decision altitude. As it is currently

written, an approach with a DA of 400 feet AFE would qualify the airport/approach to be

used for the 1-1-3 exemption.



The statement above is causing confusion.


Intended Outcome:

Revise the provision to read:

“The intended destination airport must have at least one operational CAT I ILS

approach available for use that has minimums no greater than 200’ DA(H) and 2000

RVR visibility.”


Status:  Open.  (Status of language to be provided to Leo Hollis).

Update from Industry Lead.



13.  A317. Acceptance of a Fatigue Risk Management Plan


FAA Lead:

Industry Lead:


Issue Statement:

A Fatigue Risk Management Plan (FRMP) and subsequently OpsSpec A317 are

required for all air carriers conducting operations under Title 14 of the Code of Federal

Regulations (14 CFR), part 121.



Congress has passed the Airline Safety and Federal Aviation Administration Extension

Act of 2010. Section 212(b) of the Act requires that each air carrier conducting

operations under part 121 to submit a FRMP no later than October 31, 2010.

A FRMP is an air carrier’s plan outlining policies and procedures for reducing the risks

of flightcrew member fatigue and improving flightcrew member alertness.

AFS-200 will review the air carrier’s draft FRMP to ensure that it addresses each

element required, as outlined in InFO 10017.

The draft FRMP should be accompanied by the completed FRMP Content Checklist

(InFO 10017SUP) which provides the inspector reviewing the document with the

location of the applicable policies and procedures within the air carrier’s FRMP.

The FAA will complete a review and either accept or reject the air carrier’s FRMP no

later than August 2, 2011.

Related reference material useful in preparing the FRMP:

• Advisory Circular (AC) 120-100 (as amended).

• Advisory Circular (AC) 120-103.

• Advisory Circular (AC) 120-92 (as amended).

• Advisory Circular (AC) 120-59a (as amended).

• Advisory Circular (AC) 120-66 (as amended).

• Advisory Circular (AC) 120-82 (as amended).

• Safety Alert for Operators (SAFO) 09014.

Continental Airlines FRMP was submitted to AFS-220 per the submission guidelines

and received acknowledgement on October 27, 2010 from Dale Roberts.


Intended Outcome:

AFS-200 will authorize the POI to issue operations specification (OpSpec) A317 to the

air carrier, signifying acceptance of the FRMP. AFS-200 will issue the POI specific

nonstandard text to be inserted into the OpSpec. The maximum duration of this OpSpec

will be 24 calendar-months from the date of issuance.


Status:  Open



14.  D105. Air Carrier Emergency Evacuation Systems (EES) Maintenance

Program Requirements


FAA Lead:

Industry Lead: Mike Keller


Issue Statement:

Request issue statement from Industry Lead.



Request relevant background from Industry Lead.


Intended Outcome:

Request intended outcome from Industry Lead.


Status:  New Agenda Item



15.  B036/B054: Class II Navigation

FAA Lead:

Industry Lead: John Cowan


Issue Statement:

Both of these OpSpecs include the same provision in paragraph b. (4) which refers to a

required gross navigation error check using an “airways navigation facility”. GPS is

understood to be an accepted “airways navigation facility” and as such, a clarification is

needed to prevent misunderstandings.

Additionally, while OpSpec B036 includes no reference to plotting or adherence to AC

90-79, the “job aid” inappropriately requires the Inspector to ensure that the procedures

included in the AC are used, thus causing differing expectations.



Where the FAA does not desire the operator to consider GPS as an acceptable airway

navigation facility, the clarifier “ground based” is used. Several readers have incorrectly

interpreted this provision with the same “ground based” mind set which has led to

confusion when GPS equipped aircraft are concerned.

Since a job aid for an OpSpec should not contain provisions, limitations or requirements

that are not also contained in the OpSpec, the B036 job aid should be revised to match

the OpSpec:

1. The principal operations inspector (POI) must ensure the operator’s LRN

program incorporates the practices and procedures recommended in the most

recent version of Advisory Circular (AC) 90-79, Recommended Practices and

Procedures for the Use of Electronic Long-Range Navigation, or the operator has

approved procedures equivalent to or exceeding those in AC 90-79 or other

applicable ACs.


Intended Outcome:

Clarify the provision to specify that it is referring to non GPS equipped aircraft as



b. (4) Prior to entering any airspace requiring the use of a non GPS based longrange

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.


Job aid:

The Principal Operations Inspector (POI) must ensure the operator’s LRN program

incorporates practices and procedures that include crosschecking to identify

potential navigational errors in sufficient time to prevent deviations. Advisory

Circular (AC) 90-79, Recommended Practices and Procedures for Use of Electronic

Long-Range Navigation, provides examples of such procedures but does not

represent the only means of compliance.

09/1-2/2011 OSWG 2011-04-Agenda

Page 24


b. (4) Prior to entering any airspace requiring the use of a non GPS based LRNS,

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.


Status:   Open.  (Update from Industry and FAA Leads).



16.  Closing.




Joint Session

Wed., Nov 2

9:00 – 12:00



     1.  Convene.  


         The meeting will begin with self introductions of all meeting attendees.



2.          Recognition.


     Opening remarks and recognition, (certificates of appreciation and plaques), for

     outstanding service and work on OpSpecs.



3.          Stakeholder Survey.


Ensure everyone has received a copy, reminder to fill it out and identify to whom to give the filled out survey, take any questions relating thereto.



4.          WebOPSS Update – to be briefed by Bob Davis


FAA  Lead :  Bob Davis (AFS-260)


Updates on current status, near and far term developments.  Is it possible for WebOPSS to generate a message when an expiration date is approaching?  Can WebOPSS be updated to automate data entry.


Status:   Open



5.          ICAO Register of AOCs - Progress Recent Developments: International Register of

      AOCs.   Mrs. Rommy Ulloa,  IATA,  will brief.  (Update for the briefing was

      provided/coordinated with International Civil Aviation Organization, ICAO).


FAA Lead: Danuta Pronczuk (AFS-52) for Part 129,

Industry Lead :  Henry Defalque, International Civil Aviation Organization, ICAO


a.       Late June – Pre-final Software developed
b.      Late June until mid-July – CAUC (Civil Aviation University of China)  internal student to internally do beta-testing and simulate simultaneous data entering 
c.       Late July – Present the final product to Nancy Graham/ICAO
d.      August – CAUC to come to Montreal to present the final Product

                                                             i.      Invite Canada for 1st Beta-Testing at the same time (TC – Transport                                                                           Canada-  is onboard)

                                                           ii.      Other states willing to participate: Australia, Singapore at this time.

e.      Until end of 2011 – Beta-testing with different selected States

f.        The aircraft information DB is operational since November 2010, and we hope that the Intl Registry of AOC will be operational at the end off 2011 or Q1 2012. The Civil Aviation University of China will install it on our server by mid-November... then it is  internal testing and then testing by a few States (Australia, Canada, Singapore, UAE, and hopefully a European State). (Update from Henry D., provided on 10/01/2011)


The developers are scheduled to deliver the product in November. ICAO will then install it on its servers and open it up for beta testing to the States that have volunteered for this process. Barring any major issues, it should go live as planned.  (Update from Tom Mistos, ICAO, 10-13-11).


The ICAO aircraft information database that will be linked to the AOC database is operational and contains aircraft from 22 States already with more pending (Update from Henry, July 2011).   The aircraft registry application is slowly getting more input from States. There had been two issues holding ICAO back, a bug/issue with the Excel template upload facility and the IRCA update process (those States that will be sending their input via IRCA need to sign a release form with IRCA giving them permission to send us the State’s data). The first issue has been resolved, however IRCA is still waiting for permission from many States.  (Update from Tom Mistos, ICAO, 10-13-11)


Status:   Open



6.          OpSpec A029.  Aircraft Interchange Arrangements.


FAA Lead: Danuta Pronczuk (AFS-52) for Part 129, Ricky Chitwood (AFS-220) for Part

121 and 135

Industry Lead :  Rich Carpenter for Part 121 and 135


The change corrects the definition of primary operator and the references to other paragraphs within the OpSpec A029.


Status:   Open (waiting on formal coordination comments)



7.             OpSpecs A003/C091. Airplane Authorization/ Operational Requirements Airplane Design Group VI (ADG-VI) Airplanes (Part 121).  Aircraft Authorized for Operations to the United States/Operational Requirements Airplane Design Group VI (ADG-VI) Airplanes  (Part 129)


     FAA Lead:   Jerry Ostronic (for U.S. domestic), Dave Henthorn and Danuta Pronczuk (for

     Part 129)

     Industry Lead:   David Oliver (for Part 129)


     Incorporation of A-380 and B-747-8 aircraft limitations into OpSpec A003 for Part 121, 135

     and 129.  For Part 129 this will also decommission OpSpec C091 (Operational Requirements

     Airplane Design Group VI (ADG –VI) Airplanes.


      Status:   Open



8.          OpSpec D301.   Aircraft Network Security Program (ANSP).  To be briefed by Chris

      Porfitt (AFS-360).


FAA Lead: Rochelle (Chelle) Brisco (AFS-360)

Industry Lead


This OpSpec is for air carriers or persons operating U.S. registered aircraft that have no physical partition between the entertainment and avionics, conduct upgrades to avionics wirelessly.  (Aircraft that require an ANSP include any aircraft produced or modified that require the manufacturer to provide operator guidance documentation for FAA approval, for example: the B-787-800, B-747-800, A-350, A-380, CS100 and CS300 aircraft).


This OpSpec is necessary to verify that operators have the skills, tooling, and procedures in place to accomplish the requirements of the manufacturer’s aircraft security document, and the recommended best practices appropriate to their operations.


Status:   Open



     9.   OpSpec C063   IFR RNAV 1 Departure Procedures (DP) and Standard

           Terminal Arrivals (STAR)


FAA Lead: John Swigart, AFS-470, Mike Frank (Part 129)

Industry Lead : Rich Yuknatvich (U.S. Domestic), David Oliver (Part 129)


Issue statement:

Development of RNAV DPs/STARs utilizing RNP 1.0 and RF legs on fast track



Request relevant background information from industry Lead.


Intended Outcome:

Request summary of intended outcome from Industry Lead.


Status:   Open



10.      OpSpec C055 .  Alternate Airport IFR Weather Minimums.


       FAA Lead: John Swigart, AFS-470

       Industry Lead: Jim Winkleman, Andy Newcomer (U.S. Domestic)


       Issue Statement:

       Unmonitored navaids are becoming an emerging problem, especially for longer haul




       Historically navaids have been monitored by FAA or entities designated by the FAA. As     more responsibilities are being contracted to third parties, the ability to monitor       essential navaids is no longer possible under certain circumstances. The increase in the number of     unmonitored navaids is beginning to have a negative effect on   providing reliable air      transportation.


       Intended out come:

       Develop a solution that meets the needs of both Industry and FAA.


       Status: Open (AFS-410 is looking at possibility of using RNAV approaches for alternates.

       Update on Mitre study).


   Need list of unmonitored Navaids to be sent to Industry Leads or Industry Chairman.



    11.  OpSpec C060   Category III Instrument Approach and Landing Operations,

           (Cascading Authorization)


    FAA Lead: Bryant Welch, AFS-410, Mike Frank (Part 129)

    Industry Lead: Steve Kuhar (U.S. Domestic), David Oliver (Part 129)


    Issue Statement:


   Template does not follow a logical flow for cascading authorization based on equipment


    Add standard language to the template for authorizing S.E. CAT III operations.

    RVR values in tables do not correctly reflect authorizations.

    Drop-down lists do not always contain the latest available airports or approaches.



    AFS-410 plans a revision in 2010. FedEx has submitted initial comments indicating that

    the paragraphs stating the requirements for different RVR values (c1 – c4) should all

    indicate that an operator is issued the lowest authorization and all higher RVR

    authorizations are also authorized based on operational equipment for that approach.


    Intended Outcome:

    Edit affected paragraphs to allow lowest RVR based on equipment status.

    Create selectable language for authorization of S.E. CAT III operations.

    Correct RVR values.

    Add needed airports or approaches to the drop-down lists.


    Status: Open (Update from AFS-410).



    12.  OpSpec C060   Category III Instrument Approach and Landing Operations,

           (Rollout RVR Requirements)


    FAA Lead: Bryant Welch, AFS-410, Mike Frank (Part 129)

    Industry Lead: Steve Kuhar (U.S. Domestic), David Oliver (Part 129)


    Issue Statement:


    Draft Template changes Rollout RVR requirements from advisory to Controlling.



    CAT III operations are generally approved through use of AC 120-28D. This AC

    generally supports that TDZ, MID and RO RVR are controlling; although, not in an

    entirely consistent manner. There seems to be a disconnect when comparing RVR

    requirements of AC 120-28D Table 4.3.8-1 and that provided in Appendix 7)

    Order 8900.1 appears to support Controlling/Controlling/Controlling for all systems.

    Historical context: Reference to HBAT 99-17 is inconclusive as both arguments can be

    supported depending on specific section of the HBAT being referenced.


   Intended Outcome:

   Understand historical context of the requirements of RO RVR (i.e. was it intended to be

   Controlling or Advisory)

   Ultimately from a safety standpoint, determine what is “reasonable” for RO RVR


    Change the guidance materials or OpSpec to accurately and consistently reflect the

    agreed upon RO RVR requirement.


   Status: Open (Update from AFS-410).



    13.  OpSpec C060   Category III Instrument Approach and Landing Operations,

           (Limitations/SF Lights)


    FAA Lead: Bryant Welch, AFS-410, Mike Frank (Part 129)

    Industry Lead: Steve Kuhar (U.S. Domestic), David Oliver (Part 129)


Issue Statement:

Approach lighting requirement is unnecessary.



Throughout OpSpec C060 the requirement for approach lights is qualified by statements

such as; “CAT III approaches and landings may be continued even though the

sequence flashers and the approach lights became inoperative.”

Therefore it appears that Operating Limitations section e. (2) (f) is unnecessary “ALSF-I,

ALSF-II, or SSALR approach light system or foreign equivalent. Sequence flashing

lights, may be inoperative.”

It has been pointed out many times that on a CAT III approach in actual CAT III weather

the approach lights will not be visible and will be behind the aircraft when the pilot is

able to verify that the aircraft will touch down in the touchdown zone.


Intended Outcome:

Remove the requirement for ALSF-I, ALSF-II, or SSALR approach light system or

foreign equivalent.


Status: New Agenda Item



14.      OpSpec D095  Minimum Equipment List (MEL) Authorization


FAA Lead:

Industry Lead: Mike Keller


Issue Statement:

Request issue statement from Industry Lead.



Request relevant background from Industry Lead.


Intended Outcome:

Request intended outcome from Industry Lead.


Status:  New Agenda Item



15.   OpSpec D485  - Aging Airplane Inspection and Records Review

To be briefed by Rusty Jones, AFS-320.


FAA Lead:  Rusty Jones (AFS-320), Gary Layton (AFS-52)

Industry Lead :  Mike Keller (U.S. domestic)


For Part 129, U.S. registered airplanes; a new template has been released with the associated inspector guidance updated.


New Issue :

There is no definition in the regulations nor in the FAA guidance that establishes what

the Manufacture date is, however; Industry is required to track from the Manufacture




The Aging Aircraft Safety Act of 1991 requires inspections and review of maintenance

and other records of each aircraft an air carrier uses to provide air transportation. The

manufacture date must be determined in order to fulfill the requirements of this OpSpec.


Intended Outcome:

Define a reliable means for identifying the manufacture date of an aircraft.


Status:  Open. (Update from Industry Lead.)




16.  Closing





International Session

Wed., November 2nd 

1:00 pm – 5:00 pm


1.          Convene .



2.          OpSpecs B034 and B035.  IFR Class I En Route Navigation Using Area Navigation Systems and Class I Navigation in the U.S. Class A Airspace Using Area or Long-Range Navigation Systems


FAA LeadRolfe Dinwoodie (ROC IFU) and Mike Frank (AFS-52)

Industry Lead Capt. Harold Cardona Henao, (Avianca)


Draft in process that will decommission B035 and possibly B034, incorporating the limitations into OpSpec A003.


Status:   Open





3.          OpSpec B039 – Operations in North Atlantic Minimum Navigation Performance Specifications (NAT/MNPS) Airspace With U.S. Registered Airplanes – to be briefed by Madison and Danuta


FAA Lead:  Madison Walton (AFS-470), and Danuta Pronczuk (AFS-52)

Industry Lead


Review proposed decommissioning of OpSpec B039 for foreign air carriers and persons.


Status:   Open



4.          OpSpec B046 – Operations in Reduced Vertical Separation Minimum (RVSM) Airspace of the United States and Operations in RVSM Airspace by U.S. Registered Aircraft – to be briefed by Madison and Danuta.


FAA Lead:  Madison Walton (AFS-470), Herb Herzog (ANC IFU), and Danuta Pronczuk (AFS-52)

Industry Lead


Review proposed decommissioning of OpSpec B046 for foreign air carriers and persons.


Status:   Open



5.          Part 129 Rulemaking – to be briefed by Darcy Reed.


Operations Specifications final rule published on February 10, 2011.  The final rule:

·              Removed and reserved Appendix A to Part 129,

·              Added new regulatory language to Part 129 on:  agent for service, recognition of an 83bis arrangement, OpSpecs amendment, suspension, termination and an appeal process.

The Part 129 rewrite is in Lifecycle Stage 2 (working on the Notice of Proposed Rulemaking).


Status:   Open



6.          OpSpec  A001.   Issuance and Applicability, and Reports - Incorporation of airport

list into OpSpec A001 briefed by Patrick Crowley, FAA - ANC IFU.


FAA Lead: Patrick Crowley (FAA – ANC IFU)

Industry Lead: Jacques Malot (Air France) for scheduled airports, and Brian Miles (Emirates) for nonscheduled flight notification method.


Incorporation of airport list into OpSpec A001 was made and the new template released on 06/03/2011 (revision 050 to OpSpec A001).  The non-scheduled flight notification was also incorporated.  The proposed 72 hr notification requirement was not incorporated; the language was revised as follows:


“If the foreign air carrier plans on conducting a non-scheduled flight other than a Special Interest Flight, the air carrier shall provide the responsible FSDO with advance written notice (including by facsimile, e-mail, or paper document) of the operation. For urgent situations, a telephone notification to the responsible FSDO may be used with a written notice sent as soon as possible.”

Status:   amendment has been completed.  Industry has requested that the FAA reopen the non-scheduled flight notification method for non-scheduled operations to scheduled destination airports. Extended the compliance date to December 31, 2011.




7.          OpSpecs  A006 & A007 - the combining of Foreign Air Carrier Management Personnel and other Other Designated Persons into one OpSpec.  To be briefed by David Henthorn.


FAA Lead:  David Henthorn (FAA - LAX IFO), Mike Frank (FAA – AFS-52)

Industry Lead:  Jonathan Echmalian (representing various airlines)


The new OpSpec A006 was renamed to Foreign Air carrier’s Personnel, Designated Agent, and Other Persons.  The new template has been released (09/23/2011).   This is where the new OpSpec final rule had a significant impact for the small Part 129 air carrier – all need to have a designated agent for service.


The SAFO and InFO information was not incorporated into the OpSpec.  The SAFO and InFO Orders were added to the guidance tab for OpSpec A006 in WebOPSS.  Each order has a link to where foreign air carriers and persons may go to view or subscribe to SAFO’s and InFO’s.


Added to the history for OpSpec A006, in part, the following statement:  please re-issue the A006 by 11/23/11 or at such time that a new A004 is issued (e.g. when authorizing a new optional OpSpec), whichever comes first.


Status:   Closed.




8.          OpSpec A008 - Operational Control, Aeronautical Weather, and Airport Data - the combining of OpSpec A008, A009, and A010 into one OpSpec.  To be briefed by David Henthorn, FAA - LAX IFO.


FAA Lead:  David Henthorn (FAA - LAX IFO)

Industry Lead:  Brian Miles

New template has been released in WebOPPS, inspector guidance has been updated to reflect the change.


Status: Closed




9.          OpSpecs A036 & A040 - the combining of the Traffic Alert and Collision Avoidance System (TCAS) OpSpec together with Aircraft Radio Equipment .  To be briefed by David Henthorn , FAA - LAX IFO.


FAA Lead:  David Henthorn (FAA - SFO IFO)

Industry Lead:  Eva Stahlemar (Scandinavian Airlines System)


Amended action in Notice to the following: This action must be accomplished within 90 days of the release of the revised A036 opspec in the Web-based Operations Safety System (WebOPSS), or at such time that a new OpSpec A004 is issued, (e.g. when authorizing a new optional OpSpec), whichever comes first.


Status:   Open




10.  OpSpec D085 - The incorporation of OpSpec D072 into D085.  To be briefed by Fred Sobeck (AFS-300).


FAA Lead:  George Bean (AFS-50), Fred Sobeck (AFS-300)

Industry Lead:


New template has been released in WebOPSS, the associated inspector guidance has been updated in FAA Order 8900.1 to reflect the change.


Status:  Closed




11.  OpSpec C080 - Terminal Area IFR Operations in Class G Airspace and at Airports without an Operating Control Tower.  (Combined C080 with C064).  To be briefed by Danuta Pronczuk.


FAA Lead:  Rolfe Dinwoodie (ROC and ALB IFU), Danuta Pronczuk (AFS-52)

Industry Lead:  Brian Miles (Emirates)


New template has been released in WebOPSS, the associated inspector guidance has been updated in FAA Order 8900.1 to reflect the change.


Status:  Closed



12.  OpSpecs C056 & C057– IFR Takeoff minimums all U.S. Airports and Alternate Airports for Departure – combined small and large.   To be briefed by Danuta Pronczuk, and Bryant Welch


FAA Lead:  Danuta Pronczuk (AFS-52), and Bryant Welch (AFS-400)

Industry Lead:  John Conlon (British Airways)


      This new C056 OpSpec incorporates the information from OpSpec C057 with the  

      information from OpSpec C056.  The new C056:



Status: Open.



13.  OpSpecs C075 & C076 – Category I IFR Landing Minimums – combined circling maneuvers and contact approaches at U.S. Airports.  Briefed be briefed by Mike Frank.


FAA Lead:  David Krueger (FAA - DFW IFO), Mike Frank, (AFS-52)

Industry Lead:  David Oliver (Qantas Airways Limited)


New template has been released in WebOPSS, the associated inspector guidance has been updated in FAA Order 8900.1 to reflect the change.


Status:   Closed.



14.  OpSpecs B051 & B056 - Visual Flight Rules (VFR) Limitations and Provisions – Airplanes and Helicopters.  To be briefed by Danuta Pronczuk.


FAA Lead:  Scott Schweizer (ANC IFU).

Industry Lead:  John Conlon (British Airways)


Could we move to A003 as part of limitations?


Status:   Open.



15.      OpSpec B031


FAA LeadRolfe Dinwoodie (ROC IFU), Danuta Pronczuk (AFS-52)

Industry Lead:  Jorge I. Londono A., (Tampa Cargo S.A.)


Issue:  VFR only air carriers.  Specifically, the problem is that the text in the existing template is static text, the IFR text does not apply to air carriers conducting VFR only operations and VFR enroute is covered already in A003, B051, and B056).


Status:   Open.



16.      OpSpec A028.  Aircraft Wet Lease Arrangements.


FAA Lead:  Danuta Pronczuk (AFS-52)

Industry Lead


Issue:  the term “primary” operator is used in interchange arrangements to mean something different then in wet lease.  This may confuse. 


The proposed draft eliminates any confusion as to which operator has operational and airworthiness control, eliminates the use of the term “primary” operator, and merges the two subparagraphs into one.


Status:   Open



17.  Closing