Cessna 172 pilot and ground personnel reported a critical ground conflict with a Citation jet at a non-towered airport when the pilot's headset malfunctioned and they landed opposite direction on the same runway as the jet.
Synopsis
Cessna 172 pilot and ground personnel reported a critical ground conflict with a Citation jet at a non-towered airport when the pilot's headset malfunctioned and they landed opposite direction on the same runway as the jet.
Narrative
This was a near miss on the runway...opposite direction landing on the same runway...wind was direct crosswind; so either runway was in use. I was landing when I saw another plane opposite end of runway...I took evasive action; I applied max braking and steered off the runway to avoid them...they went past me as I was off the runway. No damage; No injuries. This was a non-towered field...the pilots of the other aircraft said they were making all of their calls...which I didn't hear. I was also making all of my calls as it says to in the book (established on the RNAV XX straight in; 10 mile; 5 mile; short final). I am currently in training for my IFR rating. I was performing a practice approach into runway XX and maintaining VFR.I was plugged into the passenger jacks since the pilot side jacks did not have a functioning push to talk. I was pushing the passenger side push to talk and making my radio calls. I was on XXX.XX...I tested the coms on the ground afterwards with a member of the ground crew...this was after I had taken my equipment out of the plane. I climbed in and plugged my headset jack firmly into the passenger side jack...we started the plane and he noted that my radios were set to the right frequencies…we tried the push to talk and transmitted...it worked we noted though that it seemed really easy for the jacks to slide out...so I assume that's what caused the coms issue. I didn't have any issues transmitting or receiving on the way there.Next time ill definitely do a mic check and make sure I am heard on frequency (especially if I don't hear anyone for a while) perform an equipment check.
Second reporter narrative
In short a Cessna shot an approach for our RW XX against the flow of traffic; and making no radio calls. A single engine Diamond Star was able to depart without issue; followed by a twin Diamond. However; neither aircraft was able to see the Cessna on approach and I advised member of my line staff to warn the departing twin star of the 172s close proximity. The twin acknowledged the information and banked off to avoid the 172. During this however; a Citation was on final approach for the runway in use (RWY). The Citation landed despite this information; mere seconds after the 172 landed. The Cessna took avoiding action; veering off to their left into the grass to avoid the oncoming Citation. The Citation veered to their left; going as far as they could without going into the grass to avoid the 172. Upon both aircraft's arrival to the FBO ramp it was determined that the 172s left radio was faulty; and the pilot was using the right seat headset connection and push to talk; while still sitting in the left seat. The Citation crew stated that they were already in full reverse by the time they realized there was an aircraft on the runway. I feel it was faulty on both sides; the 172 shouldn't have been flown with faulty equipment; or from the opposite seat of the only functioning connections in the aircraft. The crew of the Citation had ample time to abort their landing; given how much time was left when we made the call on UNICOM about the aircraft with no comms. Given how frequently we have no comm landings; it is my opinion that as long as we aren't towered; these issues will continue to happen until our luck runs out; and we have an actual accident with loss of life.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.