2011-07 · NASA ASRS report 960313
TRACON Controller described a flawed visual approach clearance resulting in an overtake situation; requiring a turn by the second aircraft on final; the reporter acknowledging the spacing judgment was inaccurate.
A flight of two C130s; VFR pop-up; requested the high speed left downwind Runway XX at ZZZ. About the time I was RADAR identifying the aircraft and coordinating with the Tower for the request; I took a hand off on aircraft Y; IFR; inbound for landing at ZZZ. I had only been on position maybe 5 minutes or so. I vectored aircraft Y east southeast during the descent to make him #2. When I turned him in and cleared him for the visual approach Runway XX; I advised him that he was following the C130s and I fully expected to have the required separation to touchdown when I frequency changed him to Tower. Tower called not long afterward and coordinated a 360 for aircraft Y for spacing; which I approved. As I looked at the situation; I realized that the C130 flight had flown a wider pattern than I had expected and that aircraft Y had kept his speed up longer as well. I'm mostly certain that Aircraft Y's altitude was well above the C130s; but I'm not 100% sure. It's been nagging at me; though; that I'm not sure whether I lost wake turbulence separation or not; which is why I am choosing to report it. I should have either had Aircraft Y report the C130s in sight and instructed him to maintain visual separation or kept him wider longer before cutting him loose on the visual to ensure there was absolutely no way he could catch them. It was early in my shift and it was one of those days when I personally felt a little behind the eight ball before I even talked to any aircraft. I made the mistake of ignoring that personal indicator and not giving a little extra room as I normally would on those rare occasions I feel that way.
The RADAR Controller asked for an approval into my airspace for a flight of two C130s for a left downwind to Runway XX. I approved this operation because I had no other traffic. I then observed Aircraft Y; Citation; at 9;000 FT inbound for a visual approach to Runway XX. The C130 flight called and I cleared them to land. The RADAR Controller vectored the Citation to follow. When Aircraft Y was transferred to me they were on final. I sequenced them #2 to follow the C130s. At this point I assumed the RADAR Controller had pointed the C130s out and the Citation had them in sight and visual separation was being applied. However the Citation indicated to me that they did not have the traffic in sight. Therefore 4 miles separation would be needed for wake turbulence with a small following a large. I then instructed the Citation to make a 360 on final for spacing. I would say that the Citation was about 1 mile behind the C130s at the closest point. I really did not notice the altitude separation.Even if the Citation did see the C130s it would have resulted in a go around or the 360 turn due to the fact that the C130s need to roll to the end of the runway to exit. In my opinion; the RADAR Controller failed to do their job. I have not listened to the tapes of the event so I do not know what was said.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.