37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 445070 |
Time | |
Date | 199907 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : mlu.airport |
State Reference | LA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : mlu.tower |
Operator | common carrier : air carrier |
Make Model Name | Light Transport, Low Wing, 2 Turboprop Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | landing : roll |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : cfi |
Experience | flight time last 90 days : 150 flight time total : 2040 flight time type : 720 |
ASRS Report | 445070 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : multi engine pilot : commercial |
Events | |
Anomaly | incursion : landing without clearance non adherence : clearance non adherence : far |
Independent Detector | other controllera other flight crewa |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Scheduled flight from iah to mlu. When we were handed off from ZHU to monroe approach, we noticed they were conducting training with a new controller. We continued on in, and were held at a high altitude until cleared for the approach. Between getting down and configuring the aircraft for landing, we never received or asked for a handoff to tower. We subsequently landed without a landing clearance. No conflicts arose with other traffic. We landed, cleared the runway, and were told to contact tower. We did and their reply was to 'not worry about it.' contributing factors for us were getting busy all at once, from being held up high and having to configure. Also the controllers preoccupied with the trainee. From now on there are 2 switches that I use to remind me -- one on when cleared for the approach, and the other on when cleared to land.
Original NASA ASRS Text
Title: LTT COMMUTER LANDS MLU WITHOUT PROPER CLRNC.
Narrative: SCHEDULED FLT FROM IAH TO MLU. WHEN WE WERE HANDED OFF FROM ZHU TO MONROE APCH, WE NOTICED THEY WERE CONDUCTING TRAINING WITH A NEW CTLR. WE CONTINUED ON IN, AND WERE HELD AT A HIGH ALT UNTIL CLRED FOR THE APCH. BTWN GETTING DOWN AND CONFIGURING THE ACFT FOR LNDG, WE NEVER RECEIVED OR ASKED FOR A HDOF TO TWR. WE SUBSEQUENTLY LANDED WITHOUT A LNDG CLRNC. NO CONFLICTS AROSE WITH OTHER TFC. WE LANDED, CLRED THE RWY, AND WERE TOLD TO CONTACT TWR. WE DID AND THEIR REPLY WAS TO 'NOT WORRY ABOUT IT.' CONTRIBUTING FACTORS FOR US WERE GETTING BUSY ALL AT ONCE, FROM BEING HELD UP HIGH AND HAVING TO CONFIGURE. ALSO THE CTLRS PREOCCUPIED WITH THE TRAINEE. FROM NOW ON THERE ARE 2 SWITCHES THAT I USE TO REMIND ME -- ONE ON WHEN CLRED FOR THE APCH, AND THE OTHER ON WHEN CLRED TO LAND.
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.