 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Change in runway assignment on arrival to mht finds DC10 high on the visual glide path. Flight crew initiates descent prior to receiving clearance.
| Attributes | |
| ACN | 721553 |
| Time | |
| Date | 200612 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : mht.airport |
| State Reference | NH |
| Altitude | msl bound lower : 2000 msl bound upper : 3000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tracon : a90.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | DC-10 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Plan | IFR |
| Aircraft 2 | |
| Navigation In Use | ils localizer & glide slope : 17 |
| Flight Phase | descent : approach |
| Route In Use | approach : instrument precision approach : visual approach other arrival : on vectors |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : atp pilot : commercial pilot : flight engineer pilot : multi engine pilot : cfi |
| Experience | flight time last 90 days : 120 flight time total : 4300 flight time type : 120 |
| ASRS Report | 721553 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | altitude deviation : excursion from assigned altitude non adherence : clearance non adherence : far other anomaly |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | ATC Human Performance Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
During approach into runway 27 at mht; we received multiple heading and altitude changes. Once we tuned in the localizer for runway 17 I saw that we were above GS and started to descend prior to receiving approach clearance. Approach asked us about our altitude and subsequently cleared us for the visual approach. Upon landing tower requested we call TRACON. Human factors: we were expecting runway 35. Approach control gave us runway 24 upon initial contact. We asked for runway 35 then received runway 17. With a combination of briefing a new approach; getting our instrumentation set up; trying to look for the airport visually and finishing checklist; we got a little rushed. I saw that the GS was below us and tried to recapture forgetting that we had not been cleared! In the future I would request more time by ATC or an extended vector.
Original NASA ASRS Text
Title: CHANGE IN RWY ASSIGNMENT ON ARR TO MHT FINDS DC10 HIGH ON THE VISUAL GLIDE PATH. FLT CREW INITIATES DSCNT PRIOR TO RECEIVING CLRNC.
Narrative: DURING APCH INTO RWY 27 AT MHT; WE RECEIVED MULTIPLE HDG AND ALT CHANGES. ONCE WE TUNED IN THE LOC FOR RWY 17 I SAW THAT WE WERE ABOVE GS AND STARTED TO DSND PRIOR TO RECEIVING APCH CLRNC. APCH ASKED US ABOUT OUR ALT AND SUBSEQUENTLY CLRED US FOR THE VISUAL APCH. UPON LNDG TWR REQUESTED WE CALL TRACON. HUMAN FACTORS: WE WERE EXPECTING RWY 35. APCH CTL GAVE US RWY 24 UPON INITIAL CONTACT. WE ASKED FOR RWY 35 THEN RECEIVED RWY 17. WITH A COMBINATION OF BRIEFING A NEW APCH; GETTING OUR INSTRUMENTATION SET UP; TRYING TO LOOK FOR THE ARPT VISUALLY AND FINISHING CHKLIST; WE GOT A LITTLE RUSHED. I SAW THAT THE GS WAS BELOW US AND TRIED TO RECAPTURE FORGETTING THAT WE HAD NOT BEEN CLRED! IN THE FUTURE I WOULD REQUEST MORE TIME BY ATC OR AN EXTENDED VECTOR.
Data retrieved from NASA's ASRS site as of January 2009 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.