37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 366460 |
Time | |
Date | 199704 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : bos |
State Reference | MA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | descent : approach landing other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 210 flight time total : 13840 flight time type : 9200 |
ASRS Report | 366460 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | incursion : landing without clearance non adherence : published procedure non adherence : far |
Independent Detector | other controllera other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Operating as an air carrier flight iah-bos, we were on approach to bos at approximately XA15 when bos approach (frequency 133.0) cleared us for the visual approach to runway 33L. We continued the approach to a landing without incident. After taxiing clear of runway 33L, and attempting to contact bos tower for further clearance, I realized we were still on bos approach control (frequency 133.0). Approach had never handed us over to the tower controller and we did not realize this until after landing! Contacted bos tower on frequency 128.8 and was instructed to taxi to the gate without further comment. This occurred after flying nearly 8 hours on an 11 hour duty day. Fatigue was certainly a factor (awake 18 1/2 hours at this point). Perhaps a landing checklist with 'landing clearance received' could preclude this type of incident.
Original NASA ASRS Text
Title: AN ACR MD80 FLC LANDS WITHOUT CLRNC AT BOS, STILL ON APCH FREQ.
Narrative: OPERATING AS AN ACR FLT IAH-BOS, WE WERE ON APCH TO BOS AT APPROX XA15 WHEN BOS APCH (FREQ 133.0) CLRED US FOR THE VISUAL APCH TO RWY 33L. WE CONTINUED THE APCH TO A LNDG WITHOUT INCIDENT. AFTER TAXIING CLR OF RWY 33L, AND ATTEMPTING TO CONTACT BOS TWR FOR FURTHER CLRNC, I REALIZED WE WERE STILL ON BOS APCH CTL (FREQ 133.0). APCH HAD NEVER HANDED US OVER TO THE TWR CTLR AND WE DID NOT REALIZE THIS UNTIL AFTER LNDG! CONTACTED BOS TWR ON FREQ 128.8 AND WAS INSTRUCTED TO TAXI TO THE GATE WITHOUT FURTHER COMMENT. THIS OCCURRED AFTER FLYING NEARLY 8 HRS ON AN 11 HR DUTY DAY. FATIGUE WAS CERTAINLY A FACTOR (AWAKE 18 1/2 HRS AT THIS POINT). PERHAPS A LNDG CHKLIST WITH 'LNDG CLRNC RECEIVED' COULD PRECLUDE THIS TYPE OF INCIDENT.
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.