MD80 flight crew failed to have the current approach charts available for their scheduled destination airport due to mistakenly removing current charts when replacing revisions not yet affective.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	539588
Time
Date	200202
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : sgf.airport
State Reference	MO
Altitude	msl single value : 3000
Environment
Flight Conditions	IMC
Aircraft 1
Controlling Facilities	tracon : sgf.tracon
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : multi engine pilot : atp
Experience	flight time last 90 days : 190 flight time total : 10500 flight time type : 3000
ASRS Report	539588
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : published procedure
Independent Detector	aircraft equipment other aircraft equipment : current aero charts other flight crewa other flight crewb
Resolutory Action	controller : provided flight assist flight crew : overcame equipment problem
Consequence	other
Supplementary
Problem Areas	Chart Or Publication Flight Crew Human Performance
Primary Problem	Chart Or Publication

Narrative:

My error in posting a commercial chart revision resulted in not having proper approach plates. I replaced ILS approachs with those that were not yet effective. I inadvertently removed the VOR approach to runway 20. Due to winds only 2 approachs were legal, the VOR and ADF. The ADF did not identify. Neither my first officer or myself had the VOR approach since we both incorrectly posted the commercial chart change. We got approach plate information from RAPCON. Knowledge of the area and VOR bearing/distance from airfield diagram confirmed RAPCON information. We flew the VOR runway 20. Suggest this: commercial chart changes with different effective dates be distributed in separate changes. Have same date effective changes grouped alone and separate from others. Also highlight a change that may cause the removal of an approach.

Original NASA ASRS Text

Title: MD80 FLC FAILED TO HAVE THE CURRENT APCH CHARTS AVAILABLE FOR THEIR SCHEDULED DEST ARPT DUE TO MISTAKENLY REMOVING CURRENT CHARTS WHEN REPLACING REVISIONS NOT YET AFFECTIVE.

Narrative: MY ERROR IN POSTING A COMMERCIAL CHART REVISION RESULTED IN NOT HAVING PROPER APCH PLATES. I REPLACED ILS APCHS WITH THOSE THAT WERE NOT YET EFFECTIVE. I INADVERTENTLY REMOVED THE VOR APCH TO RWY 20. DUE TO WINDS ONLY 2 APCHS WERE LEGAL, THE VOR AND ADF. THE ADF DID NOT IDENT. NEITHER MY FO OR MYSELF HAD THE VOR APCH SINCE WE BOTH INCORRECTLY POSTED THE COMMERCIAL CHART CHANGE. WE GOT APCH PLATE INFO FROM RAPCON. KNOWLEDGE OF THE AREA AND VOR BEARING/DISTANCE FROM AIRFIELD DIAGRAM CONFIRMED RAPCON INFO. WE FLEW THE VOR RWY 20. SUGGEST THIS: COMMERCIAL CHART CHANGES WITH DIFFERENT EFFECTIVE DATES BE DISTRIBUTED IN SEPARATE CHANGES. HAVE SAME DATE EFFECTIVE CHANGES GROUPED ALONE AND SEPARATE FROM OTHERS. ALSO HIGHLIGHT A CHANGE THAT MAY CAUSE THE REMOVAL OF AN APCH.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.