37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 456710 |
Time | |
Date | 199912 |
Day | Sat |
Local Time Of Day | 0601 To 1200 |
Place | |
State Reference | WY |
Altitude | msl single value : 35000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zdv.artcc |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | cruise : level |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 7500 flight time type : 650 |
ASRS Report | 456710 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 6900 flight time type : 800 |
ASRS Report | 456366 |
Events | |
Anomaly | non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | controller : issued advisory controller : issued new clearance |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Aircraft Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
ZDV asked if we were on an assigned heading, and I (the PNF) responded 'no, we are on course' (to the bpi (big piney VOR) 035 degree radial at 38 DME fix). At this point we checked the latitude/longitude for this fix on the printed flight plan and compared it with what was programmed into the FMS and found them to be different. Upon further investigation we discovered the fix had been programmed incorrectly during preflight. We should have loaded it as: bpi 035 degree radial 38 DME. Instead it was loaded as: bpi 103 degree radial 38 DME. As the first officer, it is my job to doublechk these loaded points -- I failed to do this correctly. Fortunately, there was no airspace incursion or traffic conflict and ZDV cleared us directly to the original fix. Supplemental information from acn 456366: cleared direct bpi 035 degree radial 38 DME. Incident caused by my misreading bpi 035 degree radial as bpi 103 degree radial.
Original NASA ASRS Text
Title: AN A320 FLC IS ALERTED TO THE FACT THAT THEY ARE NOT PROCEEDING DIRECT TO THE CLRED FIX OF BPI 035 DEG RADIAL 38 DME BY ZDV, CO.
Narrative: ZDV ASKED IF WE WERE ON AN ASSIGNED HDG, AND I (THE PNF) RESPONDED 'NO, WE ARE ON COURSE' (TO THE BPI (BIG PINEY VOR) 035 DEG RADIAL AT 38 DME FIX). AT THIS POINT WE CHKED THE LATITUDE/LONGITUDE FOR THIS FIX ON THE PRINTED FLT PLAN AND COMPARED IT WITH WHAT WAS PROGRAMMED INTO THE FMS AND FOUND THEM TO BE DIFFERENT. UPON FURTHER INVESTIGATION WE DISCOVERED THE FIX HAD BEEN PROGRAMMED INCORRECTLY DURING PREFLT. WE SHOULD HAVE LOADED IT AS: BPI 035 DEG RADIAL 38 DME. INSTEAD IT WAS LOADED AS: BPI 103 DEG RADIAL 38 DME. AS THE FO, IT IS MY JOB TO DOUBLECHK THESE LOADED POINTS -- I FAILED TO DO THIS CORRECTLY. FORTUNATELY, THERE WAS NO AIRSPACE INCURSION OR TFC CONFLICT AND ZDV CLRED US DIRECTLY TO THE ORIGINAL FIX. SUPPLEMENTAL INFO FROM ACN 456366: CLRED DIRECT BPI 035 DEG RADIAL 38 DME. INCIDENT CAUSED BY MY MISREADING BPI 035 DEG RADIAL AS BPI 103 DEG RADIAL.
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.