37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 88652 |
Time | |
Date | 198806 |
Day | Sun |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : jfk |
State Reference | NY |
Altitude | msl bound lower : 2500 msl bound upper : 2500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : n90 |
Operator | common carrier : air carrier |
Make Model Name | Widebody, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other Other |
Flight Phase | climbout : initial |
Route In Use | departure sid : sid |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer observation : company check pilot |
Qualification | pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 15000 flight time type : 1000 |
ASRS Report | 88652 |
Person 2 | |
Function | flight crew : captain instruction : trainee |
Qualification | pilot : atp |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation other |
Narrative:
Took off from jfk runway 31L on a 'kennedy 1 departure, breezy point climb.' at 400' we turned left to proceed to cri VOR. (Reporter flying as supervisor in right seat performing first officer duties.) when turn towards cri VOR was initiated, I selected a 'direct to cri in FMC, CDU.' when this was executed captain flying followed command bars to fly to cri which now showed straight ahead on our HSI's. Controller asked where we were heading (kennedy departure 135.9). He advised that cri was to our 9 O'clock and gave us a left turn to 220 degrees vector. As we turned as directed, the map on our HSI's shifted and cri VOR now showed accurately. The position error caused by this map shift was significant enough to require a vector. We had taxied in heavy ground traffic at jfk for 40 mins since alignment of the HSI's. In the future, I intend to have 1 pilot in VOR mode on HSI with VOR manually selected to absolutely verify the accuracy of departure routing. The rest of the flight was routine and at the end of a 6 hour flight to san, the HSI accuracy check was right on the money and the FMC's were also right on. Callback conversation with reporter revealed the following: HSI units were aligned at gate and came up properly. Taxi to runway was extensive and much delay, 40 mins block to takeoff. One VOR NAVAID was in the manual mode and turned to cri for back up on departure. Normally they are in automatic mode for FMC updating of position. It should have been working on ground even in this condition, but sometimes with numerous aircraft around the aircraft cannot receive VOR DME signals on the ground and thus update the FMC position. Reporter talked to mfg tech rep and he stated that in europe this problem has happened and consequently some operators there are now having one set of flight instruments in the VOR mode for departures to assure position until airborne long enough to verify the FMC position is accurate.
Original NASA ASRS Text
Title: DUE TO FAULTY MAP ALIGNMENT OF FMC DISPLAY ACR WDB INCURRED TRACK DEVIATION ON DEP.
Narrative: TOOK OFF FROM JFK RWY 31L ON A 'KENNEDY 1 DEP, BREEZY POINT CLB.' AT 400' WE TURNED LEFT TO PROCEED TO CRI VOR. (RPTR FLYING AS SUPVR IN RIGHT SEAT PERFORMING F/O DUTIES.) WHEN TURN TOWARDS CRI VOR WAS INITIATED, I SELECTED A 'DIRECT TO CRI IN FMC, CDU.' WHEN THIS WAS EXECUTED CAPT FLYING FOLLOWED COMMAND BARS TO FLY TO CRI WHICH NOW SHOWED STRAIGHT AHEAD ON OUR HSI'S. CTLR ASKED WHERE WE WERE HDG (KENNEDY DEP 135.9). HE ADVISED THAT CRI WAS TO OUR 9 O'CLOCK AND GAVE US A LEFT TURN TO 220 DEGS VECTOR. AS WE TURNED AS DIRECTED, THE MAP ON OUR HSI'S SHIFTED AND CRI VOR NOW SHOWED ACCURATELY. THE POS ERROR CAUSED BY THIS MAP SHIFT WAS SIGNIFICANT ENOUGH TO REQUIRE A VECTOR. WE HAD TAXIED IN HEAVY GND TFC AT JFK FOR 40 MINS SINCE ALIGNMENT OF THE HSI'S. IN THE FUTURE, I INTEND TO HAVE 1 PLT IN VOR MODE ON HSI WITH VOR MANUALLY SELECTED TO ABSOLUTELY VERIFY THE ACCURACY OF DEP ROUTING. THE REST OF THE FLT WAS ROUTINE AND AT THE END OF A 6 HR FLT TO SAN, THE HSI ACCURACY CHK WAS RIGHT ON THE MONEY AND THE FMC'S WERE ALSO RIGHT ON. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: HSI UNITS WERE ALIGNED AT GATE AND CAME UP PROPERLY. TAXI TO RWY WAS EXTENSIVE AND MUCH DELAY, 40 MINS BLOCK TO TKOF. ONE VOR NAVAID WAS IN THE MANUAL MODE AND TURNED TO CRI FOR BACK UP ON DEP. NORMALLY THEY ARE IN AUTO MODE FOR FMC UPDATING OF POS. IT SHOULD HAVE BEEN WORKING ON GND EVEN IN THIS CONDITION, BUT SOMETIMES WITH NUMEROUS ACFT AROUND THE ACFT CANNOT RECEIVE VOR DME SIGNALS ON THE GND AND THUS UPDATE THE FMC POS. RPTR TALKED TO MFG TECH REP AND HE STATED THAT IN EUROPE THIS PROB HAS HAPPENED AND CONSEQUENTLY SOME OPERATORS THERE ARE NOW HAVING ONE SET OF FLT INSTRUMENTS IN THE VOR MODE FOR DEPS TO ASSURE POS UNTIL AIRBORNE LONG ENOUGH TO VERIFY THE FMC POS IS ACCURATE.
Data retrieved from NASA's ASRS site as of August 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.