Narrative:

My student and I were in the pattern at vti practicing takeoffs and landings; initially using runway 27 (winds were 330 at 6 knots). After 4 takeoffs and landings; we decided to switch to runway 34 since the winds were favoring 34. There was no traffic at the airport up to this point; and there had been no radio communication from other pilots in the area; although we continued to make radio calls while in the pattern.on our second landing on runway 34; just as we were rolling out on the runway after landing; we spotted an aircraft rolling down runway 9 at high speed toward the intersection with runway 34. We were clearly on a collision course; and I determined that we were unable to stop without hitting the [other aircraft]. I immediately took the controls and veered off the runway to the right into the grass to avoid hitting the other aircraft. At this point I determined that we would not be able to stop safely prior to reaching the edge of the airport boundary; so I applied full power and quickly lifted off. At that point we decided to leave the airport and head back to base.key contributors to this event:1.) the other pilot made no radio calls; even though he was monitoring the traffic frequency (he did talk on the radio afterwards saying 'oh relax' to my inquiry about not making position reports).2.) the pilot of the [other aircraft] landed runway 9 downwind in opposite direction of traffic (again without any radio calls); thus he was in a position where we were not expecting traffic.3.) the left corner of the intersection of runway 34 and 9 (as viewed from runway 34) is obscured by tall trees; thus we were unable to spot the traffic until it was almost too late.

Related reports:

Google
 

Original NASA ASRS Text

Title: C172 instructor pilot reported a NMAC with another aircraft while landing at VTI airport.

Narrative: My student and I were in the pattern at VTI practicing takeoffs and landings; initially using Runway 27 (winds were 330 at 6 knots). After 4 takeoffs and landings; we decided to switch to Runway 34 since the winds were favoring 34. There was no traffic at the airport up to this point; and there had been no radio communication from other pilots in the area; although we continued to make radio calls while in the pattern.On our second landing on Runway 34; just as we were rolling out on the runway after landing; we spotted an aircraft rolling down Runway 9 at high speed toward the intersection with Runway 34. We were clearly on a collision course; and I determined that we were unable to stop without hitting the [other aircraft]. I immediately took the controls and veered off the runway to the right into the grass to avoid hitting the other aircraft. At this point I determined that we would not be able to stop safely prior to reaching the edge of the airport boundary; so I applied full power and quickly lifted off. At that point we decided to leave the airport and head back to base.Key contributors to this event:1.) The other pilot made no radio calls; even though he was monitoring the traffic frequency (he did talk on the radio afterwards saying 'oh relax' to my inquiry about not making position reports).2.) The pilot of the [other aircraft] landed Runway 9 downwind in opposite direction of traffic (again without any radio calls); thus he was in a position where we were not expecting traffic.3.) The left corner of the intersection of Runway 34 and 9 (as viewed from Runway 34) is obscured by tall trees; thus we were unable to spot the traffic until it was almost too late.

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.