37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 501715 |
Time | |
Date | 200102 |
Day | Sat |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : lga.airport |
State Reference | NY |
Altitude | msl bound lower : 17000 msl bound upper : 17300 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : n90.tracon |
Operator | common carrier : air carrier |
Make Model Name | B737-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : intermediate altitude |
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 : 200 flight time total : 11000 flight time type : 7000 |
ASRS Report | 501715 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 6000 flight time type : 180 |
ASRS Report | 502450 |
Events | |
Anomaly | aircraft equipment problem : critical altitude deviation : overshoot non adherence : clearance other spatial deviation |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | controller : issued advisory flight crew : returned to intended or assigned course flight crew : returned to assigned altitude |
Consequence | faa : reviewed incident with flight crew other |
Factors | |
Maintenance | performance deficiency : repair performance deficiency : logbook entry performance deficiency : inspection |
Supplementary | |
Problem Areas | Flight Crew Human Performance Aircraft |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were departing on runway 31 in lga with an assignment to turn to 350 degree heading after takeoff. I had flown the airplane into lga and the first officer was flying the outbound leg. As we turned onto the runway for departure, we did not notice an approximately 30 degree heading error in our compass system. At 400 ft, I called the altitude so that the first officer would start a right turn to the 350 degree heading. As he started the turn, we were given a frequency change. I looked down to change the frequency and checked in with approach control. When I looked back at the HSI, we were on a 350 degree heading. I thought that we had completed the turn quickly, but did not suspect a problem because everything had worked normally on the leg before. We were actually flying a 320-325 degree heading. Shortly after I checked in with new york approach, we were given a heading to fly to sbj VOR. After a couple of mins, approach asked our heading and if we were going direct to sbj. I began to suspect a problem with the compass system at that time. I informed approach that we had a problem and I began to troubleshoot while the first officer was hand flying the aircraft. We were now at 17000 ft MSL. After switching between our 2 compass system, the problem still existed, so I switched to the directional gyro mode and manually slaved the compass to the wet compass heading. While I was involved with the troubleshooting, the first officer had inadvertently allowed the airplane to climb to 17300 ft. Departure control asked us to check the altitude and the first officer immediately corrected to 17000 ft. After the compass was slaved to the correct heading, we were able to navigation to tpa without any further problems. Human performance considerations: the problems that we had once airborne were really caused from not paying close enough attention to the compass system on the ground, when turning onto the runway. We had gone on duty that day at YY15 and should have been landing in tpa at XA30, but we had been delayed earlier and were just getting airborne at JA00. Lga was not busy at JA00, so that we were given an immediate clearance for takeoff. As we turned on the runway, I think I was more involved with aligning the airplane on the centerline and xferring control of the aircraft to the first officer than checking the alignment of the compass. I think that fatigue played a role as well. I had awoke at XX00 to commute over for my trip. The first officer lives in the local area, but also had arisen early. At the time of takeoff, I had been awake for 17 hours. While I felt fine, it is necessary to be more vigilant after being awake for so long. We were also late, so we were trying to get underway as quickly as possible to make up some of the time. Again, it is important to be extra vigilant under those circumstances. As for the first officer getting off the assigned altitude, it is extremely important for the PF to fly the aircraft while the PNF troubleshoots any problems. When we arrived in tpa, I wrote up the compass discrepancy in the aircraft logbook. When we flew the same aircraft later in the trip, I learned that maintenance had found that even though the first officer's compass had failed in the normal mode, his flag was frozen out of view.
Original NASA ASRS Text
Title: B732 FLC ARE ALERTED BY N90 OF HDG DISCREPANCY. DURING TROUBLESHOOTING, FO ALLOWS ACFT TO OVERSHOOT ALT.
Narrative: WE WERE DEPARTING ON RWY 31 IN LGA WITH AN ASSIGNMENT TO TURN TO 350 DEG HDG AFTER TKOF. I HAD FLOWN THE AIRPLANE INTO LGA AND THE FO WAS FLYING THE OUTBOUND LEG. AS WE TURNED ONTO THE RWY FOR DEP, WE DID NOT NOTICE AN APPROX 30 DEG HDG ERROR IN OUR COMPASS SYS. AT 400 FT, I CALLED THE ALT SO THAT THE FO WOULD START A R TURN TO THE 350 DEG HDG. AS HE STARTED THE TURN, WE WERE GIVEN A FREQ CHANGE. I LOOKED DOWN TO CHANGE THE FREQ AND CHKED IN WITH APCH CTL. WHEN I LOOKED BACK AT THE HSI, WE WERE ON A 350 DEG HDG. I THOUGHT THAT WE HAD COMPLETED THE TURN QUICKLY, BUT DID NOT SUSPECT A PROB BECAUSE EVERYTHING HAD WORKED NORMALLY ON THE LEG BEFORE. WE WERE ACTUALLY FLYING A 320-325 DEG HDG. SHORTLY AFTER I CHKED IN WITH NEW YORK APCH, WE WERE GIVEN A HDG TO FLY TO SBJ VOR. AFTER A COUPLE OF MINS, APCH ASKED OUR HDG AND IF WE WERE GOING DIRECT TO SBJ. I BEGAN TO SUSPECT A PROB WITH THE COMPASS SYS AT THAT TIME. I INFORMED APCH THAT WE HAD A PROB AND I BEGAN TO TROUBLESHOOT WHILE THE FO WAS HAND FLYING THE ACFT. WE WERE NOW AT 17000 FT MSL. AFTER SWITCHING BTWN OUR 2 COMPASS SYS, THE PROB STILL EXISTED, SO I SWITCHED TO THE DIRECTIONAL GYRO MODE AND MANUALLY SLAVED THE COMPASS TO THE WET COMPASS HDG. WHILE I WAS INVOLVED WITH THE TROUBLESHOOTING, THE FO HAD INADVERTENTLY ALLOWED THE AIRPLANE TO CLB TO 17300 FT. DEP CTL ASKED US TO CHK THE ALT AND THE FO IMMEDIATELY CORRECTED TO 17000 FT. AFTER THE COMPASS WAS SLAVED TO THE CORRECT HDG, WE WERE ABLE TO NAV TO TPA WITHOUT ANY FURTHER PROBS. HUMAN PERFORMANCE CONSIDERATIONS: THE PROBS THAT WE HAD ONCE AIRBORNE WERE REALLY CAUSED FROM NOT PAYING CLOSE ENOUGH ATTN TO THE COMPASS SYS ON THE GND, WHEN TURNING ONTO THE RWY. WE HAD GONE ON DUTY THAT DAY AT YY15 AND SHOULD HAVE BEEN LNDG IN TPA AT XA30, BUT WE HAD BEEN DELAYED EARLIER AND WERE JUST GETTING AIRBORNE AT JA00. LGA WAS NOT BUSY AT JA00, SO THAT WE WERE GIVEN AN IMMEDIATE CLRNC FOR TKOF. AS WE TURNED ON THE RWY, I THINK I WAS MORE INVOLVED WITH ALIGNING THE AIRPLANE ON THE CTRLINE AND XFERRING CTL OF THE ACFT TO THE FO THAN CHKING THE ALIGNMENT OF THE COMPASS. I THINK THAT FATIGUE PLAYED A ROLE AS WELL. I HAD AWOKE AT XX00 TO COMMUTE OVER FOR MY TRIP. THE FO LIVES IN THE LCL AREA, BUT ALSO HAD ARISEN EARLY. AT THE TIME OF TKOF, I HAD BEEN AWAKE FOR 17 HRS. WHILE I FELT FINE, IT IS NECESSARY TO BE MORE VIGILANT AFTER BEING AWAKE FOR SO LONG. WE WERE ALSO LATE, SO WE WERE TRYING TO GET UNDERWAY AS QUICKLY AS POSSIBLE TO MAKE UP SOME OF THE TIME. AGAIN, IT IS IMPORTANT TO BE EXTRA VIGILANT UNDER THOSE CIRCUMSTANCES. AS FOR THE FO GETTING OFF THE ASSIGNED ALT, IT IS EXTREMELY IMPORTANT FOR THE PF TO FLY THE ACFT WHILE THE PNF TROUBLESHOOTS ANY PROBS. WHEN WE ARRIVED IN TPA, I WROTE UP THE COMPASS DISCREPANCY IN THE ACFT LOGBOOK. WHEN WE FLEW THE SAME ACFT LATER IN THE TRIP, I LEARNED THAT MAINT HAD FOUND THAT EVEN THOUGH THE FO'S COMPASS HAD FAILED IN THE NORMAL MODE, HIS FLAG WAS FROZEN OUT OF VIEW.
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.