Meeting Agenda FAA/Aviation Industry OpSpec Working Group (OSWG) 2003-03

Information for the 2 days

(July 22 (Tuesday) 1 pm.

July 23 (Wednesday) 0830 am, 2003 ):

Meeting will be held at

Alaska Airlines' Flight Operations & Training Center.

2651 South 192nd

Seattle , WA

From the Double Tree Hotel, walk west across Pacific Hwy South (International Blvd) on 188th.  Head south when you get to 26th, the Flight Operations & Training Center is on your right (west side of 26th) and main doors are on the north west corner and south west corner of the building.  Ring door bell and tell administrative assistant that you are part of the ATA working group.  Meeting will be in Classrooms 241/242. Alaska Airlines will host a snack for our break on the 22nd and a continental type breakfast on the 23rd.

For those who don't have a crew hotel in SEA, the SeaTac Double Tree Hotel has set aside 25 rooms for our OSWG meeting in July. The hotel is within walking distance to the Alaska Airlines Flight Operations & Training Center.

Ø          Call the SeaTac Double Tree Hotel directly [206-439-6186] and

Ø          Mention you are part of the "Alaska Airlines Group Block." 

Ø          That and the set dates should get them the $53 rate. 

You may contact Erica or Ruby, 206-246-8600, or ask for Reservations, ext. 4369, or ext. 4150.  Or, World wide reservations at 1-800-222-8733, and the code works great: "Alaska Airlines Group Block for July 22-23"

Day 1

 

 

A.  Meeting Schedule/Location

July 22-23, 2003

Alaska Airlines – SEA

October 21-22, 2003

AMTI (FAA) – Washington, DC

January 20-21, 2004

American Airlines, Dallas

*April 27-28, 2004

ATA in Washington, DC

July 2004

TBA

 

B.  NEXT MEETING.  October 21/22, 2003--FAA host (Washington, DC) AMTI HQ, Floor 11

1515 Wilson Blvd ,

Arlington , VA

The list of hotels and their locations is available on the

http://www.opspecs.com website under the POLICY heading.

 

C.  OSWG “SPEC”.  Reminder that at the July meeting it will be time to review the OSWG “SPEC.”  The current SPEC is available for your review on the website http://www.opspecs.com .  The SPEC is also available on the ATA website.  This will be discussed on Wednesday morning of this meeting.

 

D.  NEW AGENDA ITEMS

 

E.  OPSPEC PARAGRAPHS DISCUSSIONS:

 

1.  OpSpec C050.  Special PIC Qualification Airports—14 CFR Section 121.445 (new)

Discussion:  Tom Penland to address the results of the subgroup solution.

OpSpec C067, Special Airports (revised), will also be revised.  A draft will be provided and the draft documents can be found on the www.opspecs.com website for review and comment.

 

Separate discussion “Island Reserves”.  As requested here is the recommendation for standardizing the fuel reserves allowed by 121.645(c) Fuel Supply, Turbine Engine Powered Airplanes, Flag and Supplemental, and 121.643(c) Fuel Supply, Nonturbine and Turbo-propeller, Supplemental Operations.  The attachment starts with a proposed change to C067 Special Airport Authorizations.. and the corresponding changes to 8400.10 paragraphs that had reference or now has reference to including "island reserves" in C067.  After consultation with Dave Burnham at UAL CMO, UAL currently uses C067 to approve these operations based on the fact that they may operate them under Flag or Supplemental rules so C067 makes the most sense.  We understand the rule says "over an approved route" but that has nothing to do with the fuel calculation and this is destination specific.  Also, a while ago we had some dialog on amending the OpSpec C067 for the listing of airports where a carrier can operate to without an available alternate.  Has anything been decided on this issue?

 

2.  OpSpec B032:  En Route Limitations and Provisions (Industry proposed revision)

DISCUSSION:  John Cowan of UAL submitted a proposed revision to B032. 

ACTION: AFS-220 suggests that we may need to update the language but the paragraph itself will not be significantly revised at this time.  The issue is not one of duplication but restrictions “unless” other authorizations are issued.

 

3.  OpSpec C058:  Special Restrictions for Foreign Terminal Instrument Procedures (guidance revision)

DISCUSSION:   Draft Order 8260.31 will be presented to the Terminal Area Operations Aviation Rulemaking Committee (TAOARC) for review and recommended action.  The National Air Carriers Association, in a December 16, 2002 letter to AFS-1, requested to have Order 8260.31 be assigned to the TAOARC for action at their next meeting (May 14-16, 2003).  The OSWG will forward comments to TAOARC collected over the last several months.  The OSWG will track the status of the draft order, however, future OSWG work on this subject will be limited to a support role to the TAOARC.

ACTION:  Jim McKie gave the 8260.31 issue to the TAOARC Chuck Guy to provide.  The document was posted on the TAOARC website for the allotted time.  The OSWG members that were selected as a part of the TAOARC subcommittee on 8260.31C to reconcile the comments received are Chuck Guy, Casey Seabright, & Jim Johnson.  They are included for the TAOARC JSC 8260.31C Action Team.  If you need a call in number, net meeting or any other kind of support, let Tom Schneider or Mike Webb ((202) 385-4603 mike.webb@faa.gov ) know and they will arrange it.  The OpSpec WG comments are at:  http://ksn-team.faa.gov/taoarc/jsc/826031C%20Library/Forms/AllItems.htm

 

4.  OpSpec C059/C359 (revised & new):  CAT II Approach Authorization

Discussion:  Jackson Seltzer raised the question of lighting equivalents, i.e. allowing a CAT II using MALSR.  Inoperative component order 6750.24D authorizes the substitution of SALSR with MALSR, why not authorize it in C059? 

According to AFS-400:  “SALSR (and especially SALS) is not an ICAO Annex 14 compliant configuration for an approach lighting system which supports CAT II operations promugated under 14 CFR Part 97.  I don't know what the basis for change to the order was, but if it is substantiated that the change in revision D is acceptable, the U.S. will have to file a notification of differences with the ICAO.

In regards to using a MALSR for CAT II operations at foreign locations, as I stated above, anything other than an ALSF-2 type of configuration, is not ICAO Annex 10 compliant and I would be surprised to see a MALSR installed at a foreign location other that a U.S. sponsored facility.  This Ops Spec change request needs to be examined.”

 

ACTION:  Look for the Order 8400.13 part of C059 to be separated out into C359.  RVR 1000 will be a selectable authorization in C059.  Connie Streeter will post a draft of the revised C059 and new C359 and associated guidance.rt of C059 to be separated out into C359.  RVR 1000 will be a selectable authorization in C059.  Connie Streeter will post a draft of the revised C059 and new C359 and associated guidance.

 

5.  CRAF Deviations, A500 OpSpec series—update

 

 

6.  E096, Weight & Balance, paragraph to be split into 3 separate paragraphs

Discussion:  Tom Penland, AFS-220.  AFS-220 is working in conjunction with the airworthiness division.  Sample of the proposed changes will be provided.

ACTION: 

 

7.   OpSpec A012, Part 121 Domestic Operations to Certain Airports Outside the 48 Contiguous States (guidance to be revised). 

DISCUSSION:  Guidance to be revised to revise the radar requirement and to emphasize the requirement for separate Economic Authority Certificate for domestic air carrier [using large aircraft] to conduct scheduled operations to foreign destinations.  Additional guidance and requirements are being developed for conducting operations with smaller aircraft over routes that include oceanic areas.  OpSpec paragraph may be revised to include the Economic Authority and overwater requirements for foreign destinations.

ACTION:   Paragraph will be re-rolled as a mandatory roll; OpSpec JobAid will indicate the change in the policy and the change in the guidance will be included in a future change to Order 8400.10.  We do not anticipate a bulletin revision since that bulletin was cancelled when the present guidance was published in change 14 to the Order 8400.10.

 

8.  OpSpec B045/B054 Single Long Range Comm/Nav (question)

Jackson Seltzer (COA) reported that the geographical area defined in paragraphs B045 and B054 do not correspond to the NY FIR/WATRS airspace. Jackson also questioned the logic of “30 minute gap” in B045 and the reasoning behind this. Exemption 2081 is the original documentation which defined the requirements for this authorization.  The preamble to incorporation of the exemption into the revision to 14 CFR Section 121.351 also lays the foundation for the 30-minute gap.  Jackson Seltzer asked if we can address the area authorized for Single LRCS in Extended Overwater Operations?  This area currently contains the gulf of Mexico which is now covered by VHF frequencies for Houston Oceanic, and Merida radio.  Additionally NY ARINC has VHF coverage across the gulf for air carrier communication with company dispatch.

ACTION:  Connie Streeter to follow up on geographical areas--The OpSpec paragraph contains exactly the same geographic areas as the original exemption 2081—which was the intent of the FAA.  Jackson to research 30 minute question and report at next meeting.

 

9.  OpSpec C089/C090 (non-std for U.S. Air only):  RNP RNAV Instrument Approaches (C300 Non-std for American Airlines)

Discussion:  Jackson Seltzer and Jim Enais provided a proposal for a standard RNP paragraph C090.

ACTION:  After discussion with the FAA, Jackson plans to revise the paragraph presented at the meeting.  The group should review the proposal for discussion at the next meeting. 

 

END of DAY ONE


 

Day 2

 

10.  SPEC Review and Adoption.

 

11.  A501/D106: Liability Insurance Suspension for Seasonal Operations or Aircraft in Long Term Storage or Long Term Maintenance

Darcy Reed, AFS-330, intended to be here to address OpSpec D106.  These new paragraphs would provide liability insurance relief to the seasonal operators (A501) and for those that were putting aircraft into long term storage.  Darcy is also developing a guidance document that addresses long-term storage aircraft maintenance. 

ACTION:  The bulletin with the guidance was released July 07, 2003, and is available on the www.opspecs.com website and in the OPSS guidance subsystem in association with both paragraphs A501 and D106.  The Ops Spec paragraphs were made available in the OPSS on Monday, July 07, 2003. 

 

12.  A010:  Aeronautical Weather Information - Connie Streeter

For Qualified Internet Provider (QICP) information

homepage

http://www2.faa.gov/ats/ars/qicp/

 

list of approved QICPs

http://www2.faa.gov/ats/ars/qicp/list%20of%20qicp.html

 

ACTION:  For issuance of OpSpec A010:  If there are no approved QICP sources listed, you will just list N/A (none available) for QICP.  There are some candidates being evaluated and the weather directorate anticipates having one or more soon.  There is no intent to hold the air carriers hostage to a requirement in which they are not able to comply with at the present time.

 

13.  A025—Electronic Recordkeeping/Electronic Flight Bag - Connie Streeter

OpSpec A025 was revised to add a new subparagraph b for the approval of the electronic flight bag.  There will also be a title change and a change in A004 statement.  NOTE:  Until the technical problem is resolved, the Table of Contents will still show the old title and the title in the paragraph will be correct.  AC 120-76A, GUIDELINES FOR THE CERTIFICATION, AIRWORTHINESS, AND OPERATIONAL APPROVAL OF ELECTRONIC FLIGHT BAG COMPUTING DEVICES, has been signed.

ACTION:  Closed

 

14B039/B059—MNPS—Santa Maria FIR, ICAO Annex 6

Connie Streeter reported that OpSpec authorization for Canadian MNPS will probably be made a separate authorization in the part 135 DB and maybe a selectable option in B059.  This is because there are part 135 operators that need only the Canadian MNPS authorization and not the NAT/MNPS.

AFS-800 and AFS-400 are now actively engaged in getting the Part 91 regulation changed to show the correct boundaries of the NAT/MNPS with the addition of the Santa Maria FIR.

ACTION: Connie Streeter coordinating with AFS-400 and AFS-200 on splitting out the MNPS for the part 135 carriers only.

 

 

15.  C066Turbojet Airplane Takeoff Operations in Tailwind Conditions Not to Exceed 15 Knots

What are the reasons for additional restrictions for 15 kt tailwind takeoff authorization.  AFM performance penalties are already restrictive. 

ACTION:  Chuck Schramek to report on follow-up with FAA performance specialists, Glenn Dail and Don Stimson.

 

16.  C074.  CAT I

Jim Winkleman raised a question about the requirements in order 8400.13 versus paragraph C074.  The order allows landing to RVR 1800 without TDZ and CL with flight director, however C074 does not.  Jim also proposed removing the table in C074 which list specific runways authorized for these operations.  It was reported that Connie Streeter, Jim Winkleman, and Casey Seabright met with Lyle Wink to discuss the guidance in the revised Order 8400.13 and a re-rsus paragraph C074.  The order allows landing to RVR 1800 without TDZ and CL with flight director, however C074 does not.  Jim also proposed removing the table in C074 which list specific runways authorized for these operations.  It was reported that Connie Streeter, Jim Winkleman, and Casey Seabright met with Lyle Wink to discuss the guidance in the revised Order 8400.13 and a re-d a re-write of the paragraph and handbook guidance. The approved airports would be published as Part 97 SIAP’s and would not require each individual carrier to demonstrate autoland to these runways. The change would also allow the approaches to be conducted via autocouple or requires flight director, etc., to 50 ft. below DH.  This came about from the FAA/JAA harmonization effort.  The JAA actually uses a percentage value which equates to 160 feet HAT.  ALPA was a key player in this compromise.

ACTION:   Lyle Wink is moving forward with the harmoni zation initiative to allow RVR 1800 minimums without TDZ and CL to be published as “Standard” instrument approach procedures which would eliminate the list of approved airports from the OpSpec paragraph. Jim Winkleman and Casey Seabright are assisting Connie Streeter in the re-write of the paragraph and supporting guidance.

 

17.  D399— Maintenance Program For Lower Landing Minima (LLM) Operations—Archived--

Connie Streeter reported that the maintenance division agreed there is no requirement for this paragraph but the following statement will be inserted into paragraphs C059 and C060 when a revision is made:  The certificate holder must maintain the aircraft and equipment listed in Table X in accordance with its approved lower landing minimums continuous maintenance program.”

ACTION:  OpSpec D399 has been archived.  Reference to the LLM Maintenance Program is being incorporated into the HB guidance for CAT II and eventually for CAT III—along with the guidance for C061 and C062.

 

18.  IOPSS.  Be advised the following DNS domain name has been established for the IOPSS (162.58.35.220) web page.  You can get to IOPSS by going to the following url:

http://iopss.faa.gov

Background:

Users of Industry OPSS, be they FAA or Industry users, need to gain access to the IOPSS system through the use of Citrix and the Internet.  To gain access to the Citrix server, users are instructed to use the following address in their web browser:  http://162.58.35.220 .  From this web page users have access to Citrix installation instructions and provides a link to the IOPSS Citrix server where they log into their respective domain. 

 

Within the last 2 months the IOPSS website has been given a "fully qualified domain name" of http://iopss.faa.gov.  This "domain name" brings our website in line with all FAA programs, with regards to internet websites, and provides an easy, 'standardized', naming convention for our users to remember.   Whether the address of  http://162.58.35.220  or  http://iopss.faa.gov  is used in the web browser, the result is the same, a web page linking internal and external users to the same Citrix server for access to Industry OPSS.

 

What does this mean to our users?  For our current users; no change is required.  For our future users and those users that don't have us added to their Favorites list; a website address that is easy to remember.