NTSB CAROL · Event
Event ERA13LA054
Aircraft involved
Probable cause & findings
The inadequate visual lookout by the pilots of both airplanes, which resulted in a midair collision.
Factual narrative
On November 10, 2012, about 1055 eastern standard time, an experimental amateur-built Vans RV-12 (RV-12), N678AD, and a Boeing E75 (Stearman), N1370V, both operated by private individuals, collided in midair while on approach to the Peach State Airport (GA2), Williamson, Georgia. The private pilot in the RV-12 and the airline transport pilot in the Stearman were not injured. Visual meteorological conditions prevailed and no flight plans were filed for either flight. The RV-12 departed the Covington Municipal Airport (CVC), Atlanta, Georgia. The Stearman departed Seven Lakes Airport (62GA), Jackson, Georgia. Both airplanes were operated as personal flights in accordance with 14 Code of Federal Regulations Part 91. Peach State airport was a privately owned, non-towered airport with an elevation of about 930 feet mean sea level (msl) and a traffic pattern attitude of 1,800 feet msl. According to a Federal Aviation Administration (FAA) inspector, a Veteran's Day celebration was being held at the airport, and the Stearman was the lead airplane in a flight of three Stearmans that planned to over-fly the airport at an altitude of 1,800 feet mean sea level (msl). The pilot of the RV-12 reported that he overflew the airport at an altitude of about 2,000 feet msl and planned to enter a right downwind for runway 13. The Stearman reported that he was flying from south to north and planned to enter a right downwind for runway 13, continue to the northwest, and maneuver back for a 360 degree turn over the runway. Both pilots stated that they communicated their respective positions and intentions over the airport's common traffic advisory frequency (CTAF). In addition, they were attempting to visually acquire each other when the two airplanes collided. Both pilots were subsequently able to land their respective airplanes without further incident. Examination of the airplanes by an FAA inspector revealed that the lower left side of the RV-12's fuselage, just aft of the cowling, and the Stearman's rudder sustained substantial damage. In addition, the RV-12's nose gear fairing also contained damage consistent with contact with the Stearman's rudder. An approximate 20-inch portion of the top of the Stearman's rudder was folded to the left about 90 degrees. A witness, who was operating the Unicom/CTAF frequency at GA2, stated that the pilot of the RV-12 reported inbound via an overhead to the right downwind for runway 13. He advised the pilot of the RV-12 of two other aircraft entering the downwind for runway 13, who then stated that he would execute a 360 and re-enter the traffic pattern. The witness was observing an airplane clear the runway after landing, when heard the pilot of the Stearman report inbound from the southeast for a practice fly-by. About 1 minute later, the pilot of the RV-12 reported entering the downwind for runway 13. He subsequently observed the Stearman approaching from the south, and the RV-12 approaching from the southeast. He asked the Stearman if they had the RV-12 insight; however, just as he released the microphone key, the two airplanes overlapped. He could not tell the approximate position of the two airplanes to each other from his vantage point, and initially believed they experienced a near-miss. The accident was not captured on radar; however, both pilots reported that they were utilizing handheld Garmin global positioning system (GPS) receivers, which were forwarded to the NTSB Vehicle Recorders Laboratory, Washington, D.C., for data download. The Stearman pilot was utilizing a Garmin GPSMAP 96C; however, flight information for the Stearman could not be extracted due to the record function having been disabled. The RV-12 pilot was utilizing a Garmin GPSMAP 496, which captured the accident flight and revealed that the RV-12 overflew the airport at a GPS altitude of about 2,400 feet and entered the downwind leg of the traffic pattern for runway 13 about 1054. The RV-12 was at a GPS altitude of about 1,800 feet, a heading of about 310 degrees, and an airspeed of about 85 knots, at the time of the collision. FAA FAR 91.113, Right-of-way rules: Except water operations, stated in part: "…(b) General. When weather conditions permit, regardless of whether an operation is conducted under instrument flight rules or visual flight rules, vigilance shall be maintained by each person operating an aircraft so as to see and avoid other aircraft.…" An amateur-built Vans RV-12 (RV-12) intended to land at the non-towered airport, while a Boeing E75 (Stearman), which was the lead airplane in a flight of three Stearmans planned to over-fly the airport at the traffic pattern altitude as part of a fly-in event being held at the airport. The pilot of the RV-12 overflew the airport at an altitude of about 600 feet above the traffic pattern altitude and entered a right downwind for runway 13. Both pilots stated that they communicated their respective positions and intentions over the airport's common traffic advisory frequency. In addition, they were attempting to visually acquire each other when the two airplanes collided. Both pilots were subsequently able to land their respective airplanes without further incident. Examination of the airplanes revealed that the lower left side of the RV-12's fuselage just aft of the cowling, and the Stearman's rudder sustained substantial damage. The damage was consistent with the RV-12 flying on a northwest heading and Stearman flying on a northerly heading, at the time of the collision. Weather permitting, each pilot was required to maintain vigilance to see and avoid other aircraft. Visual meteorological conditions prevailed at the time of the accident. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot - C
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot of other aircraft - C
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot - C
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot of other aircraft - C
Verbatim from NTSB's published report. Source file
NTSB_2012_ERA13LA054.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (midair collision). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Airspace Saturation and Midair Collision Risk: A Case Study at a Class D Airport
Near midair collisions are precursor events to actual collisions and may be an indicator of risk. While previous studies have used reports of near midair collisions to relate factors such as airspace …
- NASA NTRS 2023 · Presentation
The Viability of See-and-Avoid for Midair Collision Avoidance for Urban Air Mobility (UAM)
Urban Air Mobility (UAM) is an emerging aviation concept that could supplement today’s ground and air transportation systems.
- NASA NTRS 2023 · Presentation
The Viability of See-and-Avoid for Midair Collision Avoidance for UAM
Urban Air Mobility (UAM) is an emerging aviation concept that could supplement today’s ground and air transportation systems.
- NASA NTRS 2019 · Other - Patent
Apparatus for aiding a pilot in avoiding a midair collision between aircraft
An apparatus for aiding a pilot in avoiding a midair collision between aircraft is described. A protected aircraft carries a transmitter, a transponder, a receiver, and a data processor; and an intrud…
- Embry-Riddle Scholarly Commons 2018 · Journal article (IJAAA)
Evaluating Small UAS Near Midair Collision Risk Using AeroScope and ADS-B
As small unmanned aircraft systems (sUAS) continue to proliferate in the National Airspace System (NAS), near midair collisions are becoming more common.
- NASA NTRS 2011 · Reprint (Version printed in journal)
Midair collisions - The accidents, the systems, and the Realpolitik
Two midair collisions occurring in 1978 are described, and the air traffic control system and procedures in use at the time, human factors implications and political consequences of the accidents are …
Browse the full corpus — academia portal ↗