Narrative:

I was conducting an introductory flight. I was monitoring the CTAF when I heard an aircraft say they were departing. I did not reply with my position because I did not think I would be a factor to the airport traffic and to help with frequency congestion. I watched the aircraft lift off the runway and start its climb. After watching it climb I figured it was going to depart north because [that] runway has a standard left pattern. I kept watching [the] aircraft and it looked like it was turning south instead. Being that the aircraft was a high performance turbine aircraft I figured that the safest way to go about collision avoidance was to continue toward the airport and get inside what I thought its turn radius was. Soon after; while I was trying to get the ATIS; I lost sight of the aircraft and decided to continue straight for the airport while I tried to reestablish visual contact. I was trying to maneuver the aircraft in a right bank so that I could establish visual contact with other traffic in the area when my student pointed out that a jet just flew right under us. It looked like it was about 500 feet below us and was on a west-northwest heading. I continued and contacted approach. After contacting approach I was given the phone number to TRACON and was told to call them when I land. During the phone call with TRACON I was told the jet had to take evasive action due to TCAS (traffic collision avoidance system) RA (resolution advisory) and was asked to contact approach when flying around the class C satellite airports in the future. I believe the situation could have been avoided if I would have announced my position when the jet announced its takeoff on the CTAF or if I would have contacted approach further out from the airport.

Related reports:

Google
 

Original NASA ASRS Text

Title: C172 instructor pilot reported an NMAC with a departing corporate jet; citing poor CTAF communications as a contributing factor.

Narrative: I was conducting an introductory flight. I was monitoring the CTAF when I heard an aircraft say they were departing. I did not reply with my position because I did not think I would be a factor to the airport traffic and to help with frequency congestion. I watched the aircraft lift off the runway and start its climb. After watching it climb I figured it was going to depart north because [that] runway has a standard left pattern. I kept watching [the] aircraft and it looked like it was turning south instead. Being that the aircraft was a high performance turbine aircraft I figured that the safest way to go about collision avoidance was to continue toward the airport and get inside what I thought its turn radius was. Soon after; while I was trying to get the ATIS; I lost sight of the aircraft and decided to continue straight for the airport while I tried to reestablish visual contact. I was trying to maneuver the aircraft in a right bank so that I could establish visual contact with other traffic in the area when my student pointed out that a jet just flew right under us. It looked like it was about 500 feet below us and was on a west-northwest heading. I continued and contacted Approach. After contacting Approach I was given the phone number to TRACON and was told to call them when I land. During the phone call with TRACON I was told the jet had to take evasive action due to TCAS (Traffic Collision Avoidance System) RA (Resolution Advisory) and was asked to contact Approach when flying around the Class C satellite airports in the future. I believe the situation could have been avoided if I would have announced my position when the jet announced its takeoff on the CTAF or if I would have contacted Approach further out from the airport.

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.