37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 591728 |
Time | |
Date | 200308 |
Day | Sun |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : jfk.airport |
State Reference | NY |
Altitude | msl bound lower : 200 msl bound upper : 10000 |
Aircraft 1 | |
Controlling Facilities | tracon : n90.tracon |
Operator | common carrier : air carrier |
Make Model Name | Regional Jet CL65, Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | climbout : intermediate altitude climbout : initial climbout : takeoff |
Route In Use | departure : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 13000 flight time type : 400 |
ASRS Report | 591728 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | aircraft equipment problem : critical non adherence : published procedure non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | atc equipment other atc equipment : radar aircraft equipment other aircraft equipment : efis other controllera other flight crewa other flight crewb |
Resolutory Action | controller : issued new clearance controller : issued advisory flight crew : returned to intended or assigned course flight crew : overcame equipment problem |
Consequence | other |
Supplementary | |
Problem Areas | Aircraft Company Flight Crew Human Performance |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation |
Narrative:
Immediately after liftoff, we got heading disagreement warnings on both pilot EFIS displays. This implies a loss of heading accuracy, which was not critical at that moment. Our departure procedure simply required a turn to track directly to a VOR, then outbound on a radial. The first officer did a good job of staying focused on flying the aircraft, while I executed the normal checklists, talked to ATC, and attempted to correct our compass problem. We were well into the departure procedure, when our FMS system began warning us to 'check position.' on top of this, the compass system stubbornly resisted my attempt to fix it. Usually this is a simple toggle and switch throw. The controller then turned us to the first en route fix. When the first officer leveled the turn, I crosschecked the magnetic compass against the EFIS and completed the heading correction, which cleared the heading warning. The first officer was heading directly to the fix, but ATC called to warn us that we were not quite headed properly. She (the controller) said 'your FMS is wrong, turn 10 degrees right!' I could not tell how good or bad our FMS information was, but we did continue to have our 'check position' warning even though I had repeatedly tried to reset the system relative to local navaids. I told the controller that we had been having a heading problem. Another controller came on frequency to simply direct us to the next on course VOR. We did this on 'raw data' easily. After numerous tries, I was finally able to help the FMS find itself, and we naved successfully for the remainder of the flight using it. It is sad that our FMS and heading becomes occasionally lost in new york (especially at lga) and florida. Obviously, we are capable of flying without FMS, but the system seems to be almost predictably unreliable at times. These failures usually correct themselves, but I was caught off-guard by the persistence of this multiple failure. I should have notified ATC immediately that our FMS/heading information was suspect. I am not looking forward to using this system in IMC in highly mountainous terrain. Our company is aware of the weakness of this system.
Original NASA ASRS Text
Title: A DEP CARJ FLT CREW GETS SOME ASSISTANCE FROM DEP CTLR WHEN THEIR FMS AND DIRECTIONAL GYROS CREATE A NAV PROB FOR THEM AFTER LIFTOFF FROM JFK, NY.
Narrative: IMMEDIATELY AFTER LIFTOFF, WE GOT HEADING DISAGREEMENT WARNINGS ON BOTH PLT EFIS DISPLAYS. THIS IMPLIES A LOSS OF HEADING ACCURACY, WHICH WAS NOT CRITICAL AT THAT MOMENT. OUR DEP PROC SIMPLY REQUIRED A TURN TO TRACK DIRECTLY TO A VOR, THEN OUTBOUND ON A RADIAL. THE FO DID A GOOD JOB OF STAYING FOCUSED ON FLYING THE ACFT, WHILE I EXECUTED THE NORMAL CHKLISTS, TALKED TO ATC, AND ATTEMPTED TO CORRECT OUR COMPASS PROB. WE WERE WELL INTO THE DEP PROC, WHEN OUR FMS SYS BEGAN WARNING US TO 'CHK POS.' ON TOP OF THIS, THE COMPASS SYS STUBBORNLY RESISTED MY ATTEMPT TO FIX IT. USUALLY THIS IS A SIMPLE TOGGLE AND SWITCH THROW. THE CTLR THEN TURNED US TO THE FIRST ENRTE FIX. WHEN THE FO LEVELED THE TURN, I XCHKED THE MAGNETIC COMPASS AGAINST THE EFIS AND COMPLETED THE HEADING CORRECTION, WHICH CLRED THE HEADING WARNING. THE FO WAS HEADING DIRECTLY TO THE FIX, BUT ATC CALLED TO WARN US THAT WE WERE NOT QUITE HEADED PROPERLY. SHE (THE CTLR) SAID 'YOUR FMS IS WRONG, TURN 10 DEGS R!' I COULD NOT TELL HOW GOOD OR BAD OUR FMS INFO WAS, BUT WE DID CONTINUE TO HAVE OUR 'CHK POS' WARNING EVEN THOUGH I HAD REPEATEDLY TRIED TO RESET THE SYS RELATIVE TO LCL NAVAIDS. I TOLD THE CTLR THAT WE HAD BEEN HAVING A HEADING PROB. ANOTHER CTLR CAME ON FREQ TO SIMPLY DIRECT US TO THE NEXT ON COURSE VOR. WE DID THIS ON 'RAW DATA' EASILY. AFTER NUMEROUS TRIES, I WAS FINALLY ABLE TO HELP THE FMS FIND ITSELF, AND WE NAVED SUCCESSFULLY FOR THE REMAINDER OF THE FLT USING IT. IT IS SAD THAT OUR FMS AND HEADING BECOMES OCCASIONALLY LOST IN NEW YORK (ESPECIALLY AT LGA) AND FLORIDA. OBVIOUSLY, WE ARE CAPABLE OF FLYING WITHOUT FMS, BUT THE SYS SEEMS TO BE ALMOST PREDICTABLY UNRELIABLE AT TIMES. THESE FAILURES USUALLY CORRECT THEMSELVES, BUT I WAS CAUGHT OFF-GUARD BY THE PERSISTENCE OF THIS MULTIPLE FAILURE. I SHOULD HAVE NOTIFIED ATC IMMEDIATELY THAT OUR FMS/HEADING INFO WAS SUSPECT. I AM NOT LOOKING FORWARD TO USING THIS SYS IN IMC IN HIGHLY MOUNTAINOUS TERRAIN. OUR COMPANY IS AWARE OF THE WEAKNESS OF THIS SYS.
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.