C172 instructor reports landing on the runway as a boeing jet; approaches from the opposite directio...

Narrative:

Night cross country for private pilot certification. Ceilings and visibility was unlimited (cavok) winds were 350-06. Chain of events: my student and I were coming from the north to the south for a right 45 downwind entry for runway xxl making radio calls on CTAF for the airport after the tower closes at 2100 local. We made radio calls on the 45; downwind joining; turning base and final. We heard no one else on the frequency at the time while making those radio calls. On final approach; while approaching the threshold on runway xxl; landing lights appeared to turn on in the distance and I could not determine the type of aircraft. However the aircraft appeared to be on final for runway yyr. No radio calls were heard at the time. The reasons for continuing the landing were because I heard no one on frequency announcing intentions; we were 200 feet above the ground about 300 feet from the threshold; and if a go-around were initiated; we would be climbing out straight in the other aircraft's flight path; and a turn at low altitude would not guarantee obstacle clearance. As we touched down it became apparent the other aircraft was on short final to the opposite end of the runway. Upon touchdown; I took control of the airplane and expedited off of the runway to take evasive action. While on the ground and taxiing off the runway; the aircraft's landing lights flew over the top of us from runway yyr and it appeared to be a boeing jet making a low approach over the airport. The total distance from his aircraft and ours was maybe 100-150 feet above us as observed from our cockpit. After taxiing off the runway; we taxied to runway xxl at A5 intersection for a takeoff. After waiting for wake turbulence; announced our intentions and still heard no one on frequency. After lifting off the runway; we heard a heavy aircraft making a base turn for runway yy as he was announcing his intentions so we maneuvered to get out of his way. I believe that this is the same aircraft that made the low approach over runway yy while we were still on the runway. The first reason is because I distinctly saw the tail and body markings of the boeing as he was flying over our aircraft when we were on the ground; and saw similar markings on the aircraft that had landed on runway yy after he had landed while we were in the traffic pattern. I did not write down or remember the call sign that the aircraft used after the incident; but I do remember where he parked at and what time that he pulled off the runway. I believe that poor communication on the other aircrews' part played a major factor in the near miss. I also believe that I was not able to determine the speed and distance that the other aircraft was from the airport environment before the situation became more critical. I believe that more emphasis on communication; when possible; at a non-towered airport could have avoided this unsafe situation.

Original NASA ASRS Text

Title: C172 instructor reports landing on the runway as a Boeing jet; approaches from the opposite direction. The Boeing goes around. CTAF procedures were being used but no communications were heard from the Boeing.

Narrative: Night cross country for Private Pilot Certification. Ceilings and Visibility was unlimited (CAVOK) Winds were 350-06. Chain of events: My student and I were coming from the north to the south for a right 45 downwind entry for RWY XXL making radio calls on CTAF for the airport after the Tower closes at 2100 local. We made radio calls on the 45; downwind joining; turning base and final. We heard no one else on the frequency at the time while making those radio calls. On final approach; while approaching the threshold on Runway XXL; landing lights appeared to turn on in the distance and I could not determine the type of aircraft. However the aircraft appeared to be on final for Runway YYR. No radio calls were heard at the time. The reasons for continuing the landing were because I heard no one on frequency announcing intentions; we were 200 feet above the ground about 300 feet from the threshold; and if a go-around were initiated; we would be climbing out straight in the other aircraft's flight path; and a turn at low altitude would not guarantee obstacle clearance. As we touched down it became apparent the other aircraft was on short final to the opposite end of the runway. Upon touchdown; I took control of the airplane and expedited off of the runway to take evasive action. While on the ground and taxiing off the runway; the aircraft's landing lights flew over the top of us from Runway YYR and it appeared to be a Boeing jet making a low approach over the airport. The total distance from his aircraft and ours was maybe 100-150 feet above us as observed from our cockpit. After taxiing off the runway; we taxied to Runway XXL at A5 intersection for a takeoff. After waiting for wake turbulence; announced our intentions and still heard no one on frequency. After lifting off the runway; we heard a heavy aircraft making a base turn for Runway YY as he was announcing his intentions so we maneuvered to get out of his way. I believe that this is the same aircraft that made the low approach over Runway YY while we were still on the runway. The first reason is because I distinctly saw the tail and body markings of the Boeing as he was flying over our aircraft when we were on the ground; and saw similar markings on the aircraft that had landed on Runway YY after he had landed while we were in the traffic pattern. I did not write down or remember the call sign that the aircraft used after the incident; but I do remember where he parked at and what time that he pulled off the runway. I believe that poor communication on the other aircrews' part played a major factor in the near miss. I also believe that I was not able to determine the speed and distance that the other aircraft was from the airport environment before the situation became more critical. I believe that more emphasis on communication; when possible; at a non-towered airport could have avoided this unsafe situation.

Data retrieved from NASA's ASRS site 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.

Attributes
ACN	1189648
Time
Date	201407
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Flight Plan	None
Aircraft 2
Make Model Name	Boeing Company Undifferentiated or Other Model
Flight Phase	Final Approach
Person 1
Function	Instructor Pilot Not Flying
Qualification	Flight Crew Commercial Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor
Experience	Flight Crew Last 90 Days 60 Flight Crew Total 425 Flight Crew Type 320
Events
Anomaly	Conflict Ground Conflict Critical
Miss Distance	Vertical 150

C172 instructor reports landing on the runway as a boeing jet; approaches from the opposite direction. The boeing goes around. CTAF procedures were being used but no communications were heard from the boeing.