Date: 201902
Local time of day: 1201-1800
Location: NYL.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class D NYL
ATC / advisory: Tower NYL
Second aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Air Carrier
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict NMAC; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: My student and I were on an IFR flight plan headed back to base. We were on holding short of runway 26 at intersection K at NYL. Tower told us to line up and wait; awaiting IFR release. As we held in position; multiple C-130s; F18s; and F35s were making approaches to 21L/21R. Aircraft Y called Tower up inbound on the visual approach to Runway 26. We were told to expect an immediate departure. We acknowledged and were prepared to do so. Tower told Aircraft Y to slow to final approach speed. After what seemed like at least five minutes; maybe more; don't have exact numbers; we were cleared for takeoff. Knowing Aircraft Y was very close behind; we initiated an immediate takeoff. As we did so we passed through very obvious wake turbulence from a C-130 that had arrived on Runway 21R; one of the intersecting runways; just seconds before. As we lifted off; Aircraft Y informed Tower that they were going around because of us still being on the runway. Tower told Aircraft Y that we were clear of the runway; Aircraft Y again announced that they were still initiating a going around. Tower informed Aircraft Y that we had just started climbing out and to initiate a left downwind immediately. My student and I were watching the ADS-B traffic display as we initiated our climb and could see Aircraft Y was approaching less than a mile behind and indicating the same altitude. We leveled off at approximately 800 feet and even started a shallow descent (because we were so close to the ground) to allow Aircraft Y to climb higher than us and to avoid any further conflict. As we did so; we watched Aircraft Y pass overhead and the ADS-B traffic page showed them 400 feet above. As Aircraft Y made their left downwind turn; we were told to switch to departure. Once we were on departure frequency; the controller was advising other aircraft in the area that Tower was too busy to accept anyone for the next few minutes. The rest of the flight was uneventful. Throughout all of this; the Tower Controller seemed very task saturated with several military aircraft in the overhead pattern. At one point a C130 made a full stop landing unexpectedly which caused a fighter jet close in behind to have to go around. It seemed as if there were multiple controllers working the Tower position as well (maybe training). I think this whole situation could have been avoided a few different ways. Tower could have had us hold short of the runway while they were waiting for our IFR release. That would have freed up the runway for any other traffic (such as Aircraft Y). They probably didn't know it was going to take that long for our release though which is why they had us line up. When Aircraft Y was approaching short final; they could have told us to exit the runway back onto taxiway K or even go all the way down to taxiway L and to hold short again. Perhaps the reason for not being able to go down to taxiway L was the fact that we would have had to cross the 21R Approach safety area to do so while multiple aircraft were landing.




Synopsis: C172 Instructor Pilot reported a NMAC with a twin engine jet shortly after takeoff. The jet had executed a missed approach moments before.