C172 instructor pilot reported being on short final to runway 2 at jwn and experiencing an airborne ...

Attributes
ACN	1385343
Time
Date	201609
Local Time Of Day	0601-1200
Place
Locale Reference	JWN.Airport
State Reference	TN
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	VFR
Aircraft 2
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Route In Use	Visual Approach
Flight Plan	VFR
Person 1
Function	Pilot Flying
Qualification	Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 220 Flight Crew Total 1568 Flight Crew Type 1100
Events
Anomaly	Conflict Airborne Conflict
Miss Distance	Horizontal 1200 Vertical 200

Narrative:

I was a flight instructor giving a biennial to a private pilot. We were on our second trip around the pattern doing landing work. We made radio calls at every position (crosswind; downwind; base and final) and had another aircraft in the pattern talking to us also doing pattern training. We were on short final; just north of the river; within .3 mile of the end of runway 02 when a C172; observed at the hold short line for runway 02; proceeded to pull out onto the runway and takeoff. Their speed and distance would have created a definite mid-air collision at approximately 50 feet had we continued our landing.we had a plane on downwind so we could not immediately turn away and a large tower and helicopter traffic on our right side. We contacted the [the other aircraft doing pattern work] who moved out of the downwind to allow us to make a safe turn. The pilot causing the incursion did not make any radio calls and did not check for traffic prior to pulling out. We had all of the lights turned on; on our aircraft. Had we not taken immediate; evasive action; a mid-air collision would have occurred.

Original NASA ASRS Text

Title: C172 instructor pilot reported being on short final to Runway 2 at JWN and experiencing an airborne conflict; when another C172 pulled out onto the runway and proceeded to takeoff without announcing and apparently without looking.

Narrative: I was a flight instructor giving a biennial to a private pilot. We were on our second trip around the pattern doing landing work. We made radio calls at every position (crosswind; downwind; base and final) and had another aircraft in the pattern talking to us also doing pattern training. We were on short final; just north of the river; within .3 mile of the end of Runway 02 when a C172; observed at the hold short line for Runway 02; proceeded to pull out onto the runway and takeoff. Their speed and distance would have created a definite mid-air collision at approximately 50 feet had we continued our landing.We had a plane on downwind so we could not immediately turn away and a large tower and helicopter traffic on our right side. We contacted the [the other aircraft doing pattern work] who moved out of the downwind to allow us to make a safe turn. The pilot causing the incursion did not make any radio calls and did not check for traffic prior to pulling out. We had all of the lights turned on; on our aircraft. Had we not taken immediate; evasive action; a mid-air collision would have occurred.

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.

C172 instructor pilot reported being on short final to runway 2 at jwn and experiencing an airborne conflict; when another C172 pulled out onto the runway and proceeded to takeoff without announcing and apparently without looking.