A B757 flew to a foreign city airport that required a single engine approach that utilized an OTS VO...

Attributes
ACN	434540
Time
Date	199904
Day	199904
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : sequ.airport
State Reference	FO
Environment
Flight Conditions	IMC
Weather Elements	Fog
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B757-200
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	approach : instrument precision
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 250 flight time total : 19500 flight time type : 350
ASRS Report	434540
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : commercial pilot : instrument
Events
Anomaly	non adherence : company policies
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance Company
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After arrival in south america of our scheduled air carrier flight and during the postflt debriefing, it was discovered that the ZZZ VOR, south of the airport, was OTS. Even though our arrival procedure that evening used the YYY VOR, north of the airport, to navigation to the runway 35 ILS, an engine out missed approach (a rare possibility indeed) would have required the use of ZZZ VOR, although as an FMS/EFIS aircraft we had a real time picture of our navigation situation, our procedures into quito were based on raw data navigation due to conservative terrain considerations. Technically, we were in violation of our own operations specifications. We rechked our company flight release and found no mention of the outage, however, the navigation data NOTAM section of our commercial chart manuals did confirm the outage. The moral is: it pays to check all available information regarding a flight, and the valuable source in the commercial charts section had been overlooked.

Original NASA ASRS Text

Title: A B757 FLEW TO A FOREIGN CITY ARPT THAT REQUIRED A SINGLE ENG APCH THAT UTILIZED AN OTS VOR.

Narrative: AFTER ARR IN SOUTH AMERICA OF OUR SCHEDULED ACR FLT AND DURING THE POSTFLT DEBRIEFING, IT WAS DISCOVERED THAT THE ZZZ VOR, S OF THE ARPT, WAS OTS. EVEN THOUGH OUR ARR PROC THAT EVENING USED THE YYY VOR, N OF THE ARPT, TO NAV TO THE RWY 35 ILS, AN ENG OUT MISSED APCH (A RARE POSSIBILITY INDEED) WOULD HAVE REQUIRED THE USE OF ZZZ VOR, ALTHOUGH AS AN FMS/EFIS ACFT WE HAD A REAL TIME PICTURE OF OUR NAV SIT, OUR PROCS INTO QUITO WERE BASED ON RAW DATA NAV DUE TO CONSERVATIVE TERRAIN CONSIDERATIONS. TECHNICALLY, WE WERE IN VIOLATION OF OUR OWN OPS SPECS. WE RECHKED OUR COMPANY FLT RELEASE AND FOUND NO MENTION OF THE OUTAGE, HOWEVER, THE NAV DATA NOTAM SECTION OF OUR COMMERCIAL CHART MANUALS DID CONFIRM THE OUTAGE. THE MORAL IS: IT PAYS TO CHK ALL AVAILABLE INFO REGARDING A FLT, AND THE VALUABLE SOURCE IN THE COMMERCIAL CHARTS SECTION HAD BEEN OVERLOOKED.

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.

A B757 flew to a foreign city airport that required a single engine approach that utilized an OTS VOR.