A Tower Controller reported a NMAC between two aircraft at the same point on final approach 200 feet apart with the higher aircraft descending.

2025-10 · NASA ASRS report 2293582

Date: 2025-10 · Aircraft: Skyhawk 172/Cutlass 172 · Phase: approach

Anomalies: atc-issue-all-types|conflict-nmac|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy

Synopsis

A Tower Controller reported a NMAC between two aircraft at the same point on final approach 200 feet apart with the higher aircraft descending.

Narrative

I was in the tower cab; had just been relieved from position maybe 10 minutes before I observed a coyote on runway XX right and alerted the tower of the coyote. There was an aircraft rolling out on XX right at the time and the local controller issued the coyote traffic. There were other aircraft on final to runway XXR so the OS (Operations Supervisor) and I were watching the coyote to make sure it didn't go back on the runway. About 30 seconds later we looked left which was short final and I noticed two aircraft over the runway XXR display threshold and at first I thought the aircraft on top had to be for runway XXL; but the size of the aircraft and my experience was telling me that it was actually directly above the other aircraft who was also landing runway XXR. Just as I comprehended what I was seeing the controller working LC2 (Local Controller 2) must have seen the same thing and issued a go around to the aircraft above the other aircraft. My guess is their closest proximity was less than 50 feet. Neither aircraft reported seeing the other aircraft. After reviewing the falcon; it is clear that the two aircraft involved were in the traffic pattern and the sequence given was not followed by the pilot who inadvertently turned base directly into the aircraft they were to follow who was on final. At no point did either aircraft report the other in sight and for about a mile they were directly on top of each other; separated by 200 feet and decreasing. At the time of the event; Local Control was split and one OS was working the back and monitoring both frequencies. This is another example of needing a local assist position to help either the controller working or the OS/CIC (Controller in Charge) monitor assists position instead of making one person responsible for monitoring multiple control positions. A local assist would've been able to monitor either the coyote on the runway or assist the local controller and ensuring the aircraft he was sequencing were following his instructions.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.