 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Tower controller described a potential conflict event when traffic issued a go around failed to follow instructions to fly south of the runway; flying above traffic executing a touch and go.
| Attributes | |
| ACN | 954286 |
| Time | |
| Date | 201106 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZZZ.Tower |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Skyhawk 172/Cutlass 172 |
| Flight Phase | Climb |
| Route In Use | Visual Approach |
| Aircraft 2 | |
| Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
| Flight Phase | Landing |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
A C172 was on the runway doing a touch and go. On short final behind the C172 was a cherokee. There wasn't going to be enough spacing between the aircraft so I told the cherokee to go around south side of runway to avoid over flying the traffic on the runway. I then scanned the rest of the control environment and continued controlling my other aircraft. When I did my full scan I noticed that on the upwind of the runway the cherokee did not fully maneuver south of the runway and was right above the C172 on climb out. I immediately gave the C172 the traffic on the cherokee above and told him to make right downwind to avoid traffic. The cherokee was not answering all my transmissions and continued straight out then after a few seconds I reached him on frequency and gave him instructions back to the field. The cherokee needs to work on following instructions to avoid conflict with other aircraft.
Original NASA ASRS Text
Title: Tower Controller described a potential conflict event when traffic issued a go around failed to follow instructions to fly south of the runway; flying above traffic executing a touch and go.
Narrative: A C172 was on the runway doing a touch and go. On short final behind the C172 was a Cherokee. There wasn't going to be enough spacing between the aircraft so I told the Cherokee to go around south side of runway to avoid over flying the traffic on the runway. I then scanned the rest of the control environment and continued controlling my other aircraft. When I did my full scan I noticed that on the upwind of the runway the Cherokee did not fully maneuver south of the runway and was right above the C172 on climb out. I immediately gave the C172 the traffic on the Cherokee above and told him to make right downwind to avoid traffic. The Cherokee was not answering all my transmissions and continued straight out then after a few seconds I reached him on frequency and gave him instructions back to the field. The Cherokee needs to work on following instructions to avoid conflict with other aircraft.
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.