FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15LA210 · Aviat Inc PITTS S-2B

13 May 2015 · Tullahoma, TN, United States

Aviat Inc PITTS S-2B and Meuer Gary D V STAR · Accident: ground collision during landing

Report a problem

Event

NTSB case
ERA15LA210
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Aircraft 1 · Aviat Inc PITTS S-2B

Aircraft type
Aviat PITTS S-2B
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N110PS
Onboard fatalities
Unknown
Route
From Tullahoma Regional Airport William Northern Field (THA), Tullahoma, TNTo Tullahoma Regional Airport William Northern Field (THA), Tullahoma, TN
Aircraft age
About 19 years (built 1996)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Ground collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Aircraft 2 · Meuer Gary D V STAR

Aircraft type
Meuer Gary V STAR
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N675GM
Operator
Meuer Gary
Onboard fatalities
Unknown
Route
From Tullahoma Regional Airport William Northern Field (THA), Tullahoma, TNTo Tullahoma Regional Airport William Northern Field (THA), Tullahoma, TN
Aircraft age
About 5 years (built 2010)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Ground collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

A red V Star biplane and a white Aviat Pitts biplane collided while both airplanes were landing on the same runway. 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 1 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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15LA210
Event ID
20150514X71458
Case number
ERA15LA210
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2015-05-14.
  • API snapshot SHA-256: 8fdb1d0a4e67fafe849ce7c0b4e048abc7c778c5ef1b6e0f610b1428d1e76734; retrieved 2026-09-13T18:24:06.515Z.