37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1051892 |
Time | |
Date | 201211 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ATL.Airport |
State Reference | GA |
Aircraft 1 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
A cherokee was attempting to land at atl. On his fist attempt; and on my second transmission to the aircraft; I asked if he was familiar with the airfield; he stated no. I advised him to expect a left turn off and no delay exiting the runway. Shortly after; the aircraft turned eastbound but was approximately 1 mile north of the airport. I advised him it appeared he was not lined up with runway 8L. He stated he did not have the airport in sight. At this point he was almost abeam the threshold for runway 8L. Due to traffic behind him and his location a landing was impossible. I gave him go-around instructions and he complied appropriately. After a short delay the cherokee was now attempting a second approach; however this time there was a heavy arrival demand. Initially the cherokee was headed south-southeast. When I observed that it did not appear he was joining the runway 8L final; I queried him. He responded with an acknowledgment that led me to believe he was going to join the final. Once I realized; due to his heading; it was impossible for him to join the final; I immediately started issuing traffic for the parallel finals and attempted to turn him towards the 8L final. The cherokee reported the B757 in sight so I told him to maintain visual separation. There was also a B757 on final for runway 10 and I realized it was possible he did not see the correct aircraft so I issued that traffic as well. The cherokee was extremely close to the B757 on final for runway 9R. Around this time I realized the cherokee had lined up for runway 9L. Because I did not know the intentions of the cherokee I began breaking out a B737 who was on final for runway 8L. I told the B737 around the marker to climb to 4;000 ft and track the localizer initially; shortly their after I put the B737 on a 020 heading to avoid conflict with the cherokee (090 heading) and possible 8R departures. Initially the B737 was too far out to put on a standard 360 heading. Because of traffic on all runways; it was again; impossible for the cherokee to land. I told local 2 and 3 to stop departures. I put the cherokee on a 090 heading and climbed him to 4;000. I eventually turned him towards the north and he was handed off to the satellite position. Class B airspace should be more restrictive to GA aircraft.
Original NASA ASRS Text
Title: ATL Controller described multiple confused landing attempts by a general aviation aircraft who was apparently unfamiliar with the ATL operation; resulting in the go around of an Air Carrier.
Narrative: A Cherokee was attempting to land at ATL. On his fist attempt; and on my second transmission to the aircraft; I asked if he was familiar with the airfield; he stated no. I advised him to expect a left turn off and no delay exiting the runway. Shortly after; the aircraft turned eastbound but was approximately 1 mile north of the airport. I advised him it appeared he was not lined up with Runway 8L. He stated he did not have the airport in sight. At this point he was almost abeam the threshold for Runway 8L. Due to traffic behind him and his location a landing was impossible. I gave him go-around instructions and he complied appropriately. After a short delay the Cherokee was now attempting a second approach; however this time there was a heavy arrival demand. Initially the Cherokee was headed south-southeast. When I observed that it did not appear he was joining the Runway 8L final; I queried him. He responded with an acknowledgment that led me to believe he was going to join the final. Once I realized; due to his heading; it was impossible for him to join the final; I immediately started issuing traffic for the parallel finals and attempted to turn him towards the 8L final. The Cherokee reported the B757 in sight so I told him to maintain visual separation. There was also a B757 on final for Runway 10 and I realized it was possible he did not see the correct aircraft so I issued that traffic as well. The Cherokee was extremely close to the B757 on final for Runway 9R. Around this time I realized the Cherokee had lined up for Runway 9L. Because I did not know the intentions of the Cherokee I began breaking out a B737 who was on final for Runway 8L. I told the B737 around the marker to climb to 4;000 FT and track the localizer initially; shortly their after I put the B737 on a 020 heading to avoid conflict with the Cherokee (090 heading) and possible 8R departures. Initially the B737 was too far out to put on a standard 360 heading. Because of traffic on all runways; it was again; impossible for the Cherokee to land. I told Local 2 and 3 to stop departures. I put the Cherokee on a 090 heading and climbed him to 4;000. I eventually turned him towards the north and he was handed off to the satellite position. Class B airspace should be more restrictive to GA aircraft.
Data retrieved from NASA's ASRS site as of July 2013 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.