Date: 201911
Local time of day: 1201-1800
Location: GFK.Airport, ND
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Initial Climb
Airspace: Class D GFK
ATC / advisory: Tower GFK
Second aircraft: Small Aircraft
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Commercial
Human factors: Confusion; Situational Awareness; Training / Qualification; Workload; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Me and my student were practicing short field landings and takeoffs on GFK's Runway 17L talking to the split Tower 120.55 frequency. Tower cleared us for the option in the following stop and go. As we touched down and came to a stop; it came to my attention that an aircraft was on short final for Runway 17L behind us. Tower reiterated to us that we were 'cleared for takeoff' in what I believe was an attempt to expedite us in starting the takeoff roll.As we began our takeoff roll; the Tower Controller instructed the aircraft behind us to go around. I do not recall whether or not the controller specified 'go-around left side' or 'go-around right side' (meaning sidestep) to this aircraft; as is standard procedure in Grand Forks following an ATC directed go-around. During the initial climbout; I diverted my attention momentarily to tell my student that he was clear of the 50 feet obstacle and to correct for wind-drift more accurately as there was an aircraft going around (who would be sidestepping to avoid us). At this point we received a traffic advisory; and noticed on the traffic display that traffic was directly above us +100 feet. Immediately realizing what happened; I took flight controls and descended the aircraft while informing ATC of the traffic conflict. ATC did not respond to my report. I therefore determined that the combination of threats in the pattern (traffic volume; ATC's situational awareness; increasing wind speeds; and emotional shock from the close call) were too great to safely continue the lesson and we subsequently executed a full stop landing.In 20/20 hindsight; I should have decided to stop teaching when I recognized that an aircraft would be going around directly behind us and monitor the situation with my complete attention. This would involve planning to level off at less than pattern altitude until I could visually verify that the traffic was clear of us. Also concerning to me was the situational awareness of the other two parties involved: ATC; and the PIC of the other aircraft. Either of them had the opportunity to see that executing a go-around while tracking runway centerline would result in an imminent risk of collision; and should have: a). In the case of ATC; given instructions/advisories to either conflicting aircraft to resolve the situation. b). In the case of the other aircraft; upon hearing the takeoff clearance of an aircraft on the same runway you are going around on laterally offset the airplane to provide some separation and to aid in visual acquisition; and query ATC on the plan to maintain separation with the aircraft below.




Synopsis: Small aircraft flight instructor reported ATC instructed traffic to go-around while they were on the runway with the option.