 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
LR25 flight crew became distraction with equipment problem and climbed through assigned altitude. PIC acknowledged equipment problem, but first officer claims it never happened.
| Attributes | |
| ACN | 426001 |
| Time | |
| Date | 199901 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : bna |
| State Reference | TN |
| Altitude | msl bound lower : 23000 msl bound upper : 23800 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : mht |
| Operator | common carrier : air carrier |
| Make Model Name | Learjet 25 |
| Flight Phase | cruise other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| ASRS Report | 426001 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| ASRS Report | 426110 |
| Events | |
| Anomaly | aircraft equipment problem : less severe altitude deviation : overshoot |
| Independent Detector | other controllera |
| Resolutory Action | flight crew : returned to intended course or assigned course other |
| Consequence | Other |
| Supplementary | |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Climbing to FL230, first officer could not set up long range navigation #1. Looked down to see what problem was. When I looked back up, I was at FL235. The altitude alerter was inoperative. I called maintenance and was informed this was an intermittent problem that they could not duplicate or repair. In the future, I will try not to let unnecessary problems divert my attention during climbs and dscnts. Supplemental information from acn 426110: we were cleared to climb to FL230 by the ZME controller. A few mins later, ZME radioed us and wanted to know of our altitude. I informed ZME that we were level at FL230. The ZME controller called back and stated that he showed our altitude to be FL238. I immediately called the ZME controller and informed him that we were at FL230. At that point, the ZME controller never questioned our altitude and then handed us off to the next controller. As far as the crew is concerned, we took every step to ensure our accuracy of all sits. Regardless of whether there is a possibility of equipment malfunction (even though all system were working), it is important to always check and doublechk all areas of flight. The importance of CRM cannot be overemphasized.
Original NASA ASRS Text
Title: LR25 FLC BECAME DISTR WITH EQUIP PROB AND CLBED THROUGH ASSIGNED ALT. PIC ACKNOWLEDGED EQUIP PROB, BUT FO CLAIMS IT NEVER HAPPENED.
Narrative: CLBING TO FL230, FO COULD NOT SET UP LONG RANGE NAV #1. LOOKED DOWN TO SEE WHAT PROB WAS. WHEN I LOOKED BACK UP, I WAS AT FL235. THE ALT ALERTER WAS INOP. I CALLED MAINT AND WAS INFORMED THIS WAS AN INTERMITTENT PROB THAT THEY COULD NOT DUPLICATE OR REPAIR. IN THE FUTURE, I WILL TRY NOT TO LET UNNECESSARY PROBS DIVERT MY ATTN DURING CLBS AND DSCNTS. SUPPLEMENTAL INFO FROM ACN 426110: WE WERE CLRED TO CLB TO FL230 BY THE ZME CTLR. A FEW MINS LATER, ZME RADIOED US AND WANTED TO KNOW OF OUR ALT. I INFORMED ZME THAT WE WERE LEVEL AT FL230. THE ZME CTLR CALLED BACK AND STATED THAT HE SHOWED OUR ALT TO BE FL238. I IMMEDIATELY CALLED THE ZME CTLR AND INFORMED HIM THAT WE WERE AT FL230. AT THAT POINT, THE ZME CTLR NEVER QUESTIONED OUR ALT AND THEN HANDED US OFF TO THE NEXT CTLR. AS FAR AS THE CREW IS CONCERNED, WE TOOK EVERY STEP TO ENSURE OUR ACCURACY OF ALL SITS. REGARDLESS OF WHETHER THERE IS A POSSIBILITY OF EQUIP MALFUNCTION (EVEN THOUGH ALL SYS WERE WORKING), IT IS IMPORTANT TO ALWAYS CHK AND DOUBLECHK ALL AREAS OF FLT. THE IMPORTANCE OF CRM CANNOT BE OVEREMPHASIZED.
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.