 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Sct controller described a go around event caused by an overtake situation on final reportedly due to tail winds and flawed spacing judgement/s.
| Attributes | |
| ACN | 919253 |
| Time | |
| Date | 201011 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | SCT.TRACON |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Landing |
| Route In Use | Other Instrument Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Route In Use | Other Instrument Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
IFR; tail wind; we were running staggers. These were the first aircraft I worked. I was warned by the previous controller that there was a tailwind. I slowed both an A320 and a B737 to 220 KTS about 30 to 37 miles from the airport. The A320 was going to follow a heavy so I slowed the A320 to 180 KTS at about 10 miles in trail to the heavy. The A320 seemed to slow normally; as if the tailwind was not that bad; so I was going to let the B737 close up on the A320. I got distracted; and let the B737 get too close; so I slowed the B737 to 160 KTS. I then told the B737 that he was gaining on the A320 ahead and to slow to final. It looked like it was going to work so I switched the B737 to the tower but then the A320 slowed to about 130 KTS inside the marker. I was using the bat. The tower called and said they could not provide visual but at that time it still looked like 2.5 to me. I then gave the tower instructions to break the B737 out for re-sequencing. Recommendation; I should of stopped the B737 approach and had him go around.
Original NASA ASRS Text
Title: SCT Controller described a go around event caused by an overtake situation on final reportedly due to tail winds and flawed spacing judgement/s.
Narrative: IFR; tail wind; we were running staggers. These were the first aircraft I worked. I was warned by the previous controller that there was a tailwind. I slowed both an A320 and a B737 to 220 KTS about 30 to 37 miles from the airport. The A320 was going to follow a heavy so I slowed the A320 to 180 KTS at about 10 miles in trail to the heavy. The A320 seemed to slow normally; as if the tailwind was not that bad; so I was going to let the B737 close up on the A320. I got distracted; and let the B737 get too close; so I slowed the B737 to 160 KTS. I then told the B737 that he was gaining on the A320 ahead and to slow to final. It looked like it was going to work so I switched the B737 to the Tower but then the A320 slowed to about 130 KTS inside the marker. I was using the bat. The Tower called and said they could not provide visual but at that time it still looked like 2.5 to me. I then gave the Tower instructions to break the B737 out for re-sequencing. Recommendation; I should of stopped the B737 approach and had him go around.
Data retrieved from NASA's ASRS site as of April 2012 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.