37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1227958 |
Time | |
Date | 201412 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PHX.Tower |
State Reference | AZ |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Route In Use | None |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Flight Plan | IFR |
Person 1 | |
Function | Flight Data / Clearance Delivery |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1.7 |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Ground Incursion Runway Inflight Event / Encounter Unstabilized Approach |
Narrative:
While working clearance delivery; I was functioning as a tower team member by helping to scan the airspace and runways. I watched aircraft X make multiple s-turns on final for runway 8 due to compression with the aircraft ahead of it (aircraft Y). On one of the s-turns; the aircraft went through the final approach corridor for runway 8 and partially into runway 7R's final approach corridor; trying to build spacing between it and the aircraft ahead within a 5 mile final. The aircraft was performing low level maneuvers and was operating outside of a stabilized approach for such a low altitude.the controller; rather than initiate a go around; allowed the aircraft to cross the runway 8 threshold with aircraft Y still on the runway. Asde-X did not alarm. I observed the aircraft to be in a 10 degree bank to the right just prior to touchdown in its last ditch effort to avoid going around. The controller working local north has had multiple occurrences of not issuing go around instructions; not wanting to 'penalize' aircraft. Controller is under the impression that because the data block indicates the aircraft has visual separation with the aircraft ahead of it; that all responsibility for remaining in safe flight conditions rests with the pilot. I feel this is an extremely unsafe situation that keeps occurring.
Original NASA ASRS Text
Title: PHX Controller observes local control having an operational error and states this person doesn't want to penalize the following aircraft; so they let them land.
Narrative: While working Clearance Delivery; I was functioning as a Tower team member by helping to scan the airspace and runways. I watched Aircraft X make multiple S-turns on final for Runway 8 due to compression with the aircraft ahead of it (Aircraft Y). On one of the S-turns; the aircraft went through the final approach corridor for Runway 8 and partially into Runway 7R's final approach corridor; trying to build spacing between it and the aircraft ahead within a 5 mile final. The aircraft was performing low level maneuvers and was operating outside of a stabilized approach for such a low altitude.The controller; rather than initiate a go around; allowed the aircraft to cross the Runway 8 threshold with Aircraft Y still on the runway. ASDE-X did not alarm. I observed the aircraft to be in a 10 degree bank to the right just prior to touchdown in its last ditch effort to avoid going around. The controller working Local North has had multiple occurrences of not issuing go around instructions; not wanting to 'Penalize' aircraft. Controller is under the impression that because the data block indicates the aircraft has visual separation with the aircraft ahead of it; that all responsibility for remaining in safe flight conditions rests with the pilot. I feel this is an extremely unsafe situation that keeps occurring.
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.