37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 478529 |
Time | |
Date | 200007 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | navaid : vwv.vor |
State Reference | OH |
Altitude | msl single value : 22000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zob.artcc tracon : cvg.tracon |
Operator | common carrier : air carrier |
Make Model Name | EMB ERJ 145 ER&LR |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | cruise : level |
Route In Use | arrival star : oxi.3 |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : cfi |
Experience | flight time last 90 days : 210 flight time total : 10500 flight time type : 500 |
ASRS Report | 478529 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 4400 flight time type : 400 |
ASRS Report | 478530 |
Events | |
Anomaly | non adherence : clearance non adherence : published procedure other spatial deviation |
Independent Detector | other controllerb |
Resolutory Action | controller : issued new clearance controller : issued advisory |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Route deviation occurred on a flight from cle to ord. The filed route of flight was cle.sky.vwv.OX1.OX13.ord. The aircraft is equipped with dual FMS. While programming the FMS, the correct routing was put in up to the oxi VOR. At that point, ord was input as the destination. While programming the FMS from this point, however, the vwv transition was inadvertently added while inputting arrival and runway approach data. The FMS goes through a series of prompts, and asks when a STAR is input for a transition -- if there are any. When the prompt came up for transition, and vwv was presented, both the first officer and myself input the route via the transition -- incorrectly. Once airborne, we flew via the vwv transition for the OX13 arrival. ATC asked us our routing and I read it directly from the release. They asked how we got so far south if our route was vwv direct oxi. It took us only a min to realize what we had done. ATC gave us 3 vectors for traffic and then direct oxi. Both the first officer and myself look back on the incident and can see where the problem occurred. Unfortunately, we both agree that it could happen again easily, unless the utmost vigilance is used when programming these computers. Supplemental information from acn 478530: in the past, we have utilized the transition. Suggestions: full reading of clearance from ATC, larger print on flight plans.
Original NASA ASRS Text
Title: ACR CREW PROGRAMS FMS INCORRECTLY. ARTCC NOTICES RTE DEV.
Narrative: RTE DEV OCCURRED ON A FLT FROM CLE TO ORD. THE FILED RTE OF FLT WAS CLE.SKY.VWV.OX1.OX13.ORD. THE ACFT IS EQUIPPED WITH DUAL FMS. WHILE PROGRAMMING THE FMS, THE CORRECT ROUTING WAS PUT IN UP TO THE OXI VOR. AT THAT POINT, ORD WAS INPUT AS THE DEST. WHILE PROGRAMMING THE FMS FROM THIS POINT, HOWEVER, THE VWV TRANSITION WAS INADVERTENTLY ADDED WHILE INPUTTING ARR AND RWY APCH DATA. THE FMS GOES THROUGH A SERIES OF PROMPTS, AND ASKS WHEN A STAR IS INPUT FOR A TRANSITION -- IF THERE ARE ANY. WHEN THE PROMPT CAME UP FOR TRANSITION, AND VWV WAS PRESENTED, BOTH THE FO AND MYSELF INPUT THE RTE VIA THE TRANSITION -- INCORRECTLY. ONCE AIRBORNE, WE FLEW VIA THE VWV TRANSITION FOR THE OX13 ARR. ATC ASKED US OUR ROUTING AND I READ IT DIRECTLY FROM THE RELEASE. THEY ASKED HOW WE GOT SO FAR S IF OUR RTE WAS VWV DIRECT OXI. IT TOOK US ONLY A MIN TO REALIZE WHAT WE HAD DONE. ATC GAVE US 3 VECTORS FOR TFC AND THEN DIRECT OXI. BOTH THE FO AND MYSELF LOOK BACK ON THE INCIDENT AND CAN SEE WHERE THE PROB OCCURRED. UNFORTUNATELY, WE BOTH AGREE THAT IT COULD HAPPEN AGAIN EASILY, UNLESS THE UTMOST VIGILANCE IS USED WHEN PROGRAMMING THESE COMPUTERS. SUPPLEMENTAL INFO FROM ACN 478530: IN THE PAST, WE HAVE UTILIZED THE TRANSITION. SUGGESTIONS: FULL READING OF CLRNC FROM ATC, LARGER PRINT ON FLT PLANS.
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.