• Skip to primary navigation
  • Skip to main content
General Aviation News

General Aviation News

Because flying is cool

  • Pictures of the Day
    • Submit Picture of the Day
  • Stories
    • News
    • Features
    • Opinion
    • Products
    • NTSB Accidents
    • ASRS Reports
  • Comments
  • Classifieds
    • Place Classified Ad
  • Events
  • Digital Archives
  • Subscribe
  • Show Search
Hide Search

Planes collide on runway

By NTSB · May 15, 2017 ·

A red V Star biplane and a white Aviat Pitts biplane collided while both airplanes were landing on the same runway at the airport in Tullahoma, Tennessee.

Review of both pilot statements, a witness statement, and a video from a recorder attached to the white biplane pilot’s helmet revealed that the red biplane was ahead of the white biplane in the left airport traffic pattern.

Both pilots reported their positions on the common traffic advisory frequency; the white biplane pilot reported when he entered the downwind and final legs, and the red biplane pilot reported when he was 7 miles inbound and when he entered the downwind leg.

A review of the video showed that, for a 7-second period just before and as the white biplane was turning onto the base leg, the red biplane was visible as a small, dull, white flashing dot above trees on a flightpath consistent with entering the final leg.

The red biplane then disappeared behind the white biplane’s upper wing, but then reappeared for 4 more seconds while the white biplane was on the left base leg.

The red biplane then moved from left of the white biplane’s nose and just below the upper wing to centered just above the nose. The red biplane then disappeared below the white biplane’s cowling until one second before impact.

The white biplane was faster than the red biplane, flew a closer traffic pattern, and turned onto the base leg sooner, which resulted in the white biplane overtaking the red biplane and landing on top of it as the red biplane touched down on the runway.

Probable cause: The pilot’s inadequate visual lookout, which resulted in his airplane landing on top of the other airplane.

NTSB Identification: ERA15LA210A

This May 2015 accident report is provided by the National Transportation Safety Board. Published as an educational tool, it is intended to help pilots learn from the misfortunes of others.

About NTSB

The National Transportation Safety Board is an independent federal agency charged by Congress with investigating every civil aviation accident in the United States and significant events in the other modes of transportation, including railroad, transit, highway, marine, pipeline, and commercial space. It determines the probable causes of accidents and issues safety recommendations aimed at preventing future occurrences.

Reader Interactions

Share this story

  • Share on Twitter Share on Twitter
  • Share on Facebook Share on Facebook
  • Share on LinkedIn Share on LinkedIn
  • Share on Reddit Share on Reddit
  • Share via Email Share via Email

Become better informed pilot.

Join 110,000 readers each month and get the latest news and entertainment from the world of general aviation direct to your inbox, daily.

This field is for validation purposes and should be left unchanged.

Curious to know what fellow pilots think on random stories on the General Aviation News website? Click on our Recent Comments page to find out. Read our Comment Policy here.

Comments

  1. Paul says

    May 17, 2017 at 10:00 am

    The relative closer speed of the trailing airplane with the leading airplane should have been sufficient warning for the trailing airplane to keep the leading airplane in sight around the pattern especially when turning base and final by extending the downwind leg rather than turning inside the slower airplane on base and final. As soon as the trailing airplane lost sight of the leading airplane that should have been an immediate cue to go around rather than keep pressing on. Once the leading airplane disappeared beneath the trailing airplane’s nose a midair collision was almost certain to happen.

  2. CJ says

    May 16, 2017 at 8:32 am

    Looks like the old “box kite theory you can’t see sh#t”. When entering the traffic pattern look at what traffic is there. If communication is available use it. If one can’t see the others as questions give accurate position locations. Next stay back and follow the lead plane and keep a safe distance.

  3. John says

    May 16, 2017 at 7:50 am

    This accident is a good illustration of the fallacy of ‘see and avoid’. The pilot of the Pitts entered the pattern and landed in trail behind the white V Star (note that the GA News article has the colors reversed above). While the V Star approach speed was about 45 kts the Pitts came in ‘stabilized’ at about 80 kts. The Pitts pilot had a helmet mounted GoPro that captured VERY faint images of the landing V Star below and ahead at several points in the 20 seconds or so landing sequence for the Pitts. The GoPro recorded multiple head movements by the Pitts pilot as he searched for traffic, eyes clearly “outside”. Despite his efforts the Pitts pilot never spotted the V Star on final, and remained unaware of the V Star’s position ahead and below him until the Pitt’s prop chopped up the V Star and seriously injured its pilot. What a tragedy, and what a reminder that even our best efforts at ‘see and avoid’ may be insufficient. I suggest those who want the full tale take a look at the Docket where the NTSB has both a real time analysis of this relative positions of these aircraft, and a very chilling plot of their relative positions. Anyone who thinks NORDO in the pattern is ‘safe’ should read this accident report and supporting documents very closely.

    • Dale L. Weir says

      May 20, 2017 at 10:27 am

      Not sure what NORDO has to do with this accident since all the participants were using radios.
      Some errors in judgment and loss of situational awareness seem more appropriate.

© 2025 Flyer Media, Inc. All rights reserved. Privacy Policy.

  • About
  • Advertise
  • Comment Policy
  • Contact Us
  • Privacy Policy
  • Writer’s Guidelines
  • Photographer’s Guidelines