37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 596823 |
Time | |
Date | 200309 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : cfb.vortac |
State Reference | NY |
Altitude | msl single value : 15000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zny.artcc |
Operator | common carrier : air carrier |
Make Model Name | Regional Jet 200 ER&LR |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | climbout : intermediate altitude |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : commercial pilot : flight engineer pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 13000 flight time type : 200 |
ASRS Report | 596823 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | aircraft equipment problem : critical non adherence : far non adherence : published procedure other anomaly other other spatial deviation |
Independent Detector | aircraft equipment other aircraft equipment : fms dir msg other controllera |
Resolutory Action | controller : issued alert controller : issued new clearance |
Consequence | other |
Supplementary | |
Problem Areas | Aircraft Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Departed syr, during climb out received an FMS 'dr' message. Tried to reset with no luck. Was given instruction from ZNY to fly direct cfb. We used the FMS. While xchking position with raw data VOR information, ny called and asked our heading to confirm direct cfb. He advised us that our heading was not even close and that we were about 15 mi west of the VOR instead of 15 mi north (which is what we thought). He gave us a heading to cfb while we switched off the FMS and flew to cfb using VOR instead of FMS. There was no separation problem with other aircraft in the area although the controller was busy. When the FMS occurred we should have switched off the FMS navigation immediately. We were mislead because of the perceived accuracy, plus we were VFR. I did not believe the error was that great or that great of an error could occur that fast. I believe that I learned a valuable lesson.
Original NASA ASRS Text
Title: CRJ200 CREW CONTINUED TO USE A MALFUNCTIONING FMS AND HAD A TRACK DEV IN ZNY CLASS E.
Narrative: DEPARTED SYR, DURING CLBOUT RECEIVED AN FMS 'DR' MESSAGE. TRIED TO RESET WITH NO LUCK. WAS GIVEN INSTRUCTION FROM ZNY TO FLY DIRECT CFB. WE USED THE FMS. WHILE XCHKING POS WITH RAW DATA VOR INFO, NY CALLED AND ASKED OUR HEADING TO CONFIRM DIRECT CFB. HE ADVISED US THAT OUR HEADING WAS NOT EVEN CLOSE AND THAT WE WERE ABOUT 15 MI W OF THE VOR INSTEAD OF 15 MI N (WHICH IS WHAT WE THOUGHT). HE GAVE US A HEADING TO CFB WHILE WE SWITCHED OFF THE FMS AND FLEW TO CFB USING VOR INSTEAD OF FMS. THERE WAS NO SEPARATION PROB WITH OTHER ACFT IN THE AREA ALTHOUGH THE CTLR WAS BUSY. WHEN THE FMS OCCURRED WE SHOULD HAVE SWITCHED OFF THE FMS NAV IMMEDIATELY. WE WERE MISLEAD BECAUSE OF THE PERCEIVED ACCURACY, PLUS WE WERE VFR. I DID NOT BELIEVE THE ERROR WAS THAT GREAT OR THAT GREAT OF AN ERROR COULD OCCUR THAT FAST. I BELIEVE THAT I LEARNED A VALUABLE LESSON.
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.