Narrative:

I was in a PA20-125 with a student doing takeoff and lndgs to a full stop. The runway we were using was runway 36. We held at the beginning of the runway to let a C152 depart runway 10 after just back-taxiing. The 2 runways intersect. As we departed, we kept the C152 in sight and widened our pattern to accommodate the C152 and observe other traffic and the C152. When on final the C152 was taxiing back after landing. The C152 was on a parallel taxiway. We then saw he was holding short of our runway. We then touched down and were rolling past the tree line which blocked the view of half of runway 10. I then spotted a twin-engine which just landed on runway 10. A collision course was set. We then applied maximum brakes. Braking took place 200-300 ft, until 10-15 ft before the intersection of runway 10 where our plane went over on its back. As the tail came up I told the student to watch the brakes but he continued. The probable cause or factor was a straight-in approach of the twin which disrupted traffic flow. Also, the tree line which blocks the view for about 1200-1500 ft of the runway. Maximum braking was needed to avoid collision. In order to avoid overbraking was hard to avoid. A more clear procedure was needed prior to the training lesson. Introducing such scenarios to future students will be of much use. This was an uncontrolled field and abnormal traffic patterns will be an issue. Perhaps the twin should have been spotted on a 1 or 2 mi final but that is debatable. We were equipped with no radio but were constantly looking for traffic when we could. Luckily we were not injured and the plane only received minor damage.

Related reports:

Google
 

Original NASA ASRS Text

Title: INSTRUCTOR PLT WITH SPI ON LNDG ROLLOUT SIGHTS A TWIN ENG ACFT ON LNDG ROLL ON INTERSECTING RWY. HARD BRAKING RESULTS IN THE TAIL WHEEL ACFT FLIPPING OVER.

Narrative: I WAS IN A PA20-125 WITH A STUDENT DOING TKOF AND LNDGS TO A FULL STOP. THE RWY WE WERE USING WAS RWY 36. WE HELD AT THE BEGINNING OF THE RWY TO LET A C152 DEPART RWY 10 AFTER JUST BACK-TAXIING. THE 2 RWYS INTERSECT. AS WE DEPARTED, WE KEPT THE C152 IN SIGHT AND WIDENED OUR PATTERN TO ACCOMMODATE THE C152 AND OBSERVE OTHER TFC AND THE C152. WHEN ON FINAL THE C152 WAS TAXIING BACK AFTER LNDG. THE C152 WAS ON A PARALLEL TXWY. WE THEN SAW HE WAS HOLDING SHORT OF OUR RWY. WE THEN TOUCHED DOWN AND WERE ROLLING PAST THE TREE LINE WHICH BLOCKED THE VIEW OF HALF OF RWY 10. I THEN SPOTTED A TWIN-ENG WHICH JUST LANDED ON RWY 10. A COLLISION COURSE WAS SET. WE THEN APPLIED MAX BRAKES. BRAKING TOOK PLACE 200-300 FT, UNTIL 10-15 FT BEFORE THE INTXN OF RWY 10 WHERE OUR PLANE WENT OVER ON ITS BACK. AS THE TAIL CAME UP I TOLD THE STUDENT TO WATCH THE BRAKES BUT HE CONTINUED. THE PROBABLE CAUSE OR FACTOR WAS A STRAIGHT-IN APCH OF THE TWIN WHICH DISRUPTED TFC FLOW. ALSO, THE TREE LINE WHICH BLOCKS THE VIEW FOR ABOUT 1200-1500 FT OF THE RWY. MAX BRAKING WAS NEEDED TO AVOID COLLISION. IN ORDER TO AVOID OVERBRAKING WAS HARD TO AVOID. A MORE CLR PROC WAS NEEDED PRIOR TO THE TRAINING LESSON. INTRODUCING SUCH SCENARIOS TO FUTURE STUDENTS WILL BE OF MUCH USE. THIS WAS AN UNCTLED FIELD AND ABNORMAL TFC PATTERNS WILL BE AN ISSUE. PERHAPS THE TWIN SHOULD HAVE BEEN SPOTTED ON A 1 OR 2 MI FINAL BUT THAT IS DEBATABLE. WE WERE EQUIPPED WITH NO RADIO BUT WERE CONSTANTLY LOOKING FOR TFC WHEN WE COULD. LUCKILY WE WERE NOT INJURED AND THE PLANE ONLY RECEIVED MINOR DAMAGE.

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.