37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 191561 |
Time | |
Date | 199110 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : clt |
State Reference | NC |
Altitude | msl bound lower : 10000 msl bound upper : 10400 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : clt |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other Other |
Flight Phase | descent other |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 210 flight time total : 8000 flight time type : 1600 |
ASRS Report | 191561 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Events | |
Anomaly | altitude deviation : crossing restriction not met altitude deviation : undershoot non adherence : clearance |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I was receiving extensive vectors from center when passing through FL180 and qnh was not selected. Center had told us to intercept a radial off the clt VOR. The radial was several mi behind us and in our rush to punch in all the data required to intercept a simple radial, we overlooked the change. Local altimeter setting was high and we crossed shine approximately 400 ft high. Solution: could have gone direct to shine with 3 button pushes, (total time = 2 seconds and simple procedure), which is what the controller really wanted as shine is on the radial. Frequency was too congested to request this. Radial setup requires 20 separate, accurate keystrokes, assuming FMC is happy with the pace of data input and assuming 1 of the 2 points is not behind your aircraft. Controllers need more education concerning automated aircraft. '/Right' as an aircraft code should be different for automated aircraft. This would help the controllers, particularly departure at lga. Better cockpit discipline. Better software.
Original NASA ASRS Text
Title: ACR ALTDEV UNDERSHOT XING RESTRICTION BECAUSE THE FLC FAILED TO SET ALTIMETERS TO QFE XING THE TRANSITION LEVEL.
Narrative: I WAS RECEIVING EXTENSIVE VECTORS FROM CENTER WHEN PASSING THROUGH FL180 AND QNH WAS NOT SELECTED. CENTER HAD TOLD US TO INTERCEPT A RADIAL OFF THE CLT VOR. THE RADIAL WAS SEVERAL MI BEHIND US AND IN OUR RUSH TO PUNCH IN ALL THE DATA REQUIRED TO INTERCEPT A SIMPLE RADIAL, WE OVERLOOKED THE CHANGE. LCL ALTIMETER SETTING WAS HIGH AND WE CROSSED SHINE APPROX 400 FT HIGH. SOLUTION: COULD HAVE GONE DIRECT TO SHINE WITH 3 BUTTON PUSHES, (TOTAL TIME = 2 SECONDS AND SIMPLE PROC), WHICH IS WHAT THE CTLR REALLY WANTED AS SHINE IS ON THE RADIAL. FREQ WAS TOO CONGESTED TO REQUEST THIS. RADIAL SETUP REQUIRES 20 SEPARATE, ACCURATE KEYSTROKES, ASSUMING FMC IS HAPPY WITH THE PACE OF DATA INPUT AND ASSUMING 1 OF THE 2 POINTS IS NOT BEHIND YOUR ACFT. CTLRS NEED MORE EDUCATION CONCERNING AUTOMATED ACFT. '/R' AS AN ACFT CODE SHOULD BE DIFFERENT FOR AUTOMATED ACFT. THIS WOULD HELP THE CTLRS, PARTICULARLY DEP AT LGA. BETTER COCKPIT DISCIPLINE. BETTER SOFTWARE.
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.