Flight Instructor and their solo student reported a NMAC occurred when the student turned base leg too early in front of another Flight Instructor's aircraft on short final.

Date: 2023-12 · Aircraft: Light Sport Aircraft · Phase: approach

Anomalies: conflict-nmac|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance

Synopsis

Flight Instructor and their solo student reported a NMAC occurred when the student turned base leg too early in front of another Flight Instructor's aircraft on short final.

Narrative

I am a CFI out of ZZZ airport. I had a student pilot flying solo operating under part 61 reported to me that he had a NMAC. He told me the Tower advised him to call and they did file a report. He explained to me that he was on a right downwind leg for Runway XX and the Tower told him 'Aircraft X you are following Cessna traffic ahead report them in sight' he then reported the traffic in sight on short final. The tower told him 'Aircraft X follow the Cessna traffic on final; clear to land Runway XX' he then read back the clearance and as he felt appropriate made a turn to base leg. At some point on base leg the ATC controller called out 'Aircraft X traffic alert less than one mile.' he report the traffic on final in sight and told me he slightly descended and continued straight ahead on base and eventually made a left turn away from the airport. The other aircraft involved report they have avoided the traffic and would like to continue straight in for Runway XX. At this point ATC gave him a phone number for the Tower to copy which he wrote down. He then requested a full stop landing and called the Tower after which they told him they will need to file a report for Possible Pilot Deviation. When the tower told him to follow traffic on final and report them in sight; he saw a Cessna on short final but what he didn't realize at the time the tower told him 'Aircraft X follow Cessna traffic on a 3 mile final and to report them in sight' he overlooked the 3 mile final call and mistook the traffic on short final for being the correct traffic to follow. He then turned base which resulted in him cutting off the 3 mile final traffic which he was supposed to follow resulting in a possible NMAC.

Second reporter narrative

Paperwork is being filed on this event. This report is being written in the interest of transparency and taking full ownership of my error. This was a student solo training flight with the objective to practice short field landings by doing touch and goes in the pattern. On my first pattern (downwind for [Runway] XX) I was told to extend my downwind for traffic on final. I spotted traffic landing on [Runway] XX and told the controller that I had 'traffic in sight'. He cleared me for touch and go on [Runway] XX following the traffic. My error was identifying the wrong traffic. I turned onto base; cutting in front of the traffic that I should have been following. Upon completing my base turn I spotted the traffic in the distance and continued on a perpendicular course to that of the approaching aircraft. At that moment the controller alerted us and evasive action was taken. I was given a number to call for a possible pilot deviation. I discontinued the flight; landed; and called the tower immediately after engine shutdown. Upon hearing the audio replay; it was egregiously evident that this mishap was completely my fault. On downwind the controller stated that the traffic was on a 3 mile final. Clearly not the landing traffic that I reported as 'in sight'. One contributing factor was that I had gotten distracted by a higher than normal voltage reading when the call was made - pilot fixation. I also realize that my communication in the pattern had become too routine and automatic. I have grounded myself from solo flight until I receive additional training on traffic pattern awareness; ATC communications and avoiding distractions. I am fully aware of the gravity of my mistake and will never make it again.

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