Narrative:

Flight was being conducted as a training flight with student being the PF. ASOS reported winds as being 'calm.' traffic level was low, and traffic had been using both runways 17 and 35. Since runway 17 is generally used as the calm wind runway, we taxied to the run-up area for runway 17. After completing our run-up, we checked for traffic visually, and on the CTAF. One aircraft, a PA28 had just turned downwind for runway 35 as we taxied into position, and commenced our takeoff run. We were well above normal rotation speed, around 65 KTS, and had still not broken ground. At this point, the PA28 was on a short base to final. When I saw the PA28 on final, I took control of the aircraft, and rotated. I then immediately turned to the left in order to avoid the other aircraft. The PA28 had initiated a go around by now, and passed to our right with approximately 100 ft between our wingtips. Several factors contributed to the conflict. The fact that the airport is uncontrolled means that all traffic does not always use the same runway, especially when the wind is light or variable. According to the airport facility director, there is no calm wind runway, but runway 17 is generally used. Another factor in this situation was the PA28's closer than usual positioning of its base leg. My student allowed an unusually long takeoff run. This was not anticipated. Ultimately, if the PA28 was allowed to land before we took off, the conflict would not have happened.

Google
 

Original NASA ASRS Text

Title: INSTRUCTOR PLT AND STUDENT ON TKOF ROLL AT GLE ENCOUNTER A PA28 LNDG ON THE OPPOSITE END OF THE RWY RESULTING IN A NEAR MISS.

Narrative: FLT WAS BEING CONDUCTED AS A TRAINING FLT WITH STUDENT BEING THE PF. ASOS RPTED WINDS AS BEING 'CALM.' TFC LEVEL WAS LOW, AND TFC HAD BEEN USING BOTH RWYS 17 AND 35. SINCE RWY 17 IS GENERALLY USED AS THE CALM WIND RWY, WE TAXIED TO THE RUN-UP AREA FOR RWY 17. AFTER COMPLETING OUR RUN-UP, WE CHKED FOR TFC VISUALLY, AND ON THE CTAF. ONE ACFT, A PA28 HAD JUST TURNED DOWNWIND FOR RWY 35 AS WE TAXIED INTO POS, AND COMMENCED OUR TKOF RUN. WE WERE WELL ABOVE NORMAL ROTATION SPD, AROUND 65 KTS, AND HAD STILL NOT BROKEN GND. AT THIS POINT, THE PA28 WAS ON A SHORT BASE TO FINAL. WHEN I SAW THE PA28 ON FINAL, I TOOK CTL OF THE ACFT, AND ROTATED. I THEN IMMEDIATELY TURNED TO THE L IN ORDER TO AVOID THE OTHER ACFT. THE PA28 HAD INITIATED A GAR BY NOW, AND PASSED TO OUR R WITH APPROX 100 FT BTWN OUR WINGTIPS. SEVERAL FACTORS CONTRIBUTED TO THE CONFLICT. THE FACT THAT THE ARPT IS UNCTLED MEANS THAT ALL TFC DOES NOT ALWAYS USE THE SAME RWY, ESPECIALLY WHEN THE WIND IS LIGHT OR VARIABLE. ACCORDING TO THE ARPT FACILITY DIRECTOR, THERE IS NO CALM WIND RWY, BUT RWY 17 IS GENERALLY USED. ANOTHER FACTOR IN THIS SIT WAS THE PA28'S CLOSER THAN USUAL POSITIONING OF ITS BASE LEG. MY STUDENT ALLOWED AN UNUSUALLY LONG TKOF RUN. THIS WAS NOT ANTICIPATED. ULTIMATELY, IF THE PA28 WAS ALLOWED TO LAND BEFORE WE TOOK OFF, THE CONFLICT WOULD NOT HAVE HAPPENED.

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