37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1413257 |
Time | |
Date | 201612 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ASE.Airport |
State Reference | CO |
Aircraft 1 | |
Make Model Name | Medium Transport |
Flight Phase | Landing |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Small Aircraft High Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 119 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | VFR |
Person 1 | |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (mon) 9 |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe Conflict Ground Conflict Less Severe Deviation - Procedural Clearance |
Narrative:
Aircraft X was landing runway 15 with aircraft Y in the left downwind for runway 15. I issued aircraft Y traffic on aircraft X and aircraft Y reported traffic in sight. I told aircraft Y to follow the traffic and issued a landing clearance. Aircraft X landed and was told the exit at A5 or A6 and to expedite off the runway. Aircraft Y was coming in quickly behind aircraft X and aircraft X was not exiting fast enough so aircraft Y was issued a go around. Aircraft Y asked me to repeat myself and I told him again to go around. Aircraft Y didn't and landed runway 15 with aircraft X somewhere between A5 and A6. Aircraft Y exited at A2 and was issued a brasher with ground control. When he called the tower; he said that there was an equipment problem that made him unable to execute the go-around.aircraft Y's equipment problem might be considered an emergency situation due to it preventing him to execute a go around. Equipment problems like that should be made known to the controller so that the controller can accommodate.
Original NASA ASRS Text
Title: Aspen Tower Controller reported of a runway incursion where an arrival was told to go around due to arrival traffic on the runway. The second aircraft landed and did not go-around as instructed. Pilot reported an equipment problem after landing.
Narrative: Aircraft X was landing Runway 15 with aircraft Y in the left downwind for Runway 15. I issued aircraft Y traffic on aircraft X and aircraft Y reported traffic in sight. I told aircraft Y to follow the traffic and issued a landing clearance. Aircraft X landed and was told the exit at A5 or A6 and to expedite off the runway. Aircraft Y was coming in quickly behind aircraft X and aircraft X was not exiting fast enough so aircraft Y was issued a go around. Aircraft Y asked me to repeat myself and I told him again to go around. Aircraft Y didn't and landed Runway 15 with aircraft X somewhere between A5 and A6. Aircraft Y exited at A2 and was issued a Brasher with Ground Control. When he called the Tower; he said that there was an equipment problem that made him unable to execute the go-around.Aircraft Y's equipment problem might be considered an emergency situation due to it preventing him to execute a go around. Equipment problems like that should be made known to the controller so that the controller can accommodate.
Data retrieved from NASA's ASRS site 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.