37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 640392 |
Time | |
Date | 200412 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | navaid : col.vor |
State Reference | NJ |
Altitude | msl single value : 23000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zny.artcc |
Operator | general aviation : corporate |
Make Model Name | Citation II S2/Bravo |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : intermediate altitude |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 120 flight time total : 3000 flight time type : 700 |
ASRS Report | 640392 |
Person 2 | |
Function | flight crew : first officer |
Events | |
Anomaly | non adherence : clearance non adherence : far other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance flight crew : became reoriented |
Supplementary | |
Problem Areas | Aircraft Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Departing mmu, we were vectored to intercept the col VOR radial leading to white intersection. We were subsequently cleared direct white. Our normal navigation system FMS was out for repairs. Hence we were 'slant alpha equipment' (VOR/DME only). Up until this point, on prior legs, we were repeatedly reminding controllers we were 'slant a' and had limited ability to go direct, but could take headings. After a while, this became annoying and controllers were frustrated with us, since they tend to assume all jets can go direct anywhere. I decided to use our back-up GPS which is panel mounted, but approved only for VFR use. I dialed up white intersection and pressed 'direct.' I either pulled up the wrong intersection or read the bearing wrong, and told the PF to turn to a westerly heading. As we turned, I realized my error and told him to begin turning back southward. Simultaneously, the controller told us to turn to 170 degrees and asked why we'd turned west. He gave no traffic alerts and was calm. Also, TCASII gave no warnings and showed no traffic in our vicinity. Still I lost situational awareness and it could have been a problem. Contributing factors were lack of normal FMS capability and reliance on long neglected VOR/DME skills, fatigue (early morning wake-up for first leg), and reliance on a back-up VFR GPS. I am not used to using a possibly out-of-date database. Ultimately, I should have continued to query the controller for headings until able to navigation with our 'slant a' limitations (VOR/DME). Controllers should also note equipment codes and treat aircraft accordingly, lest they are tempted to use equipment they really should not.
Original NASA ASRS Text
Title: THE PLT OF A C550 WITH THE FMS REMOVED UTILIZED A VFR ONLY GPS FOR NAV AND TURNED TO AN INCORRECT HDG WHEN CLRED DIRECT TO A FIX.
Narrative: DEPARTING MMU, WE WERE VECTORED TO INTERCEPT THE COL VOR RADIAL LEADING TO WHITE INTXN. WE WERE SUBSEQUENTLY CLRED DIRECT WHITE. OUR NORMAL NAV SYS FMS WAS OUT FOR REPAIRS. HENCE WE WERE 'SLANT ALPHA EQUIP' (VOR/DME ONLY). UP UNTIL THIS POINT, ON PRIOR LEGS, WE WERE REPEATEDLY REMINDING CTLRS WE WERE 'SLANT A' AND HAD LIMITED ABILITY TO GO DIRECT, BUT COULD TAKE HDGS. AFTER A WHILE, THIS BECAME ANNOYING AND CTLRS WERE FRUSTRATED WITH US, SINCE THEY TEND TO ASSUME ALL JETS CAN GO DIRECT ANYWHERE. I DECIDED TO USE OUR BACK-UP GPS WHICH IS PANEL MOUNTED, BUT APPROVED ONLY FOR VFR USE. I DIALED UP WHITE INTXN AND PRESSED 'DIRECT.' I EITHER PULLED UP THE WRONG INTXN OR READ THE BEARING WRONG, AND TOLD THE PF TO TURN TO A WESTERLY HDG. AS WE TURNED, I REALIZED MY ERROR AND TOLD HIM TO BEGIN TURNING BACK SOUTHWARD. SIMULTANEOUSLY, THE CTLR TOLD US TO TURN TO 170 DEGS AND ASKED WHY WE'D TURNED W. HE GAVE NO TFC ALERTS AND WAS CALM. ALSO, TCASII GAVE NO WARNINGS AND SHOWED NO TFC IN OUR VICINITY. STILL I LOST SITUATIONAL AWARENESS AND IT COULD HAVE BEEN A PROB. CONTRIBUTING FACTORS WERE LACK OF NORMAL FMS CAPABILITY AND RELIANCE ON LONG NEGLECTED VOR/DME SKILLS, FATIGUE (EARLY MORNING WAKE-UP FOR FIRST LEG), AND RELIANCE ON A BACK-UP VFR GPS. I AM NOT USED TO USING A POSSIBLY OUT-OF-DATE DATABASE. ULTIMATELY, I SHOULD HAVE CONTINUED TO QUERY THE CTLR FOR HDGS UNTIL ABLE TO NAV WITH OUR 'SLANT A' LIMITATIONS (VOR/DME). CTLRS SHOULD ALSO NOTE EQUIP CODES AND TREAT ACFT ACCORDINGLY, LEST THEY ARE TEMPTED TO USE EQUIP THEY REALLY SHOULD NOT.
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.