NTSB CAROL · Event
Event CEN16LA283
Registry · N167BL
FAA Aircraft Registry record.
Make / Model
BRM AERO S R O BRISTELL E-LSA
Year of manufacture
2016 · 0 years old at event
Engine
ROTAX 912 IS (100 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
20160607
ADS-B equipped
Yes — Mode-S A10BD3
Registrant of record
SPORT FLYING USA INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s exceedance of the airplane’s critical angle of attack on short final approach, which resulted in an inadvertent aerodynamic stall and subsequent loss of control. Contributing to the accident was the pilot’s distraction with other traffic in the area.
Factual narrative
On July 24, 2016, at 1805 central daylight time, a BRM Aero S R O, Bristell E-LSA, collided with the terrain following a loss of control while landing at the Wittman Regional Airport (OSH), Oshkosh, Wisconsin. The pilot received serious injuries. The airplane was substantially damaged. The aircraft was registered to Sport Flying USA, Inc., and was operated by an individual under the provisions of 14 Code of Federal Regulations Part 91 as a business flight. Visual meteorological conditions prevailed for the flight, which was not operated on a flight plan. The last leg of the cross country flight originated from the Watertown Municipal Airport (RYV), Watertown, Wisconsin, at 1630.The airplane was the trailing airplane in a flight of two that were landing on runway 36L at OSH during Experimental Aircraft Association AirVenture. The pilot in the lead aircraft stated they were cleared to land on the purple dot. The purple dot was located 3,052 ft down the 8,002 ft long runway. He did not see the accident occur. The accident pilot stated he turned onto final approach for runway 36L, and was established with 20 ° of flaps at 65 knots. He then heard an air traffic transmission telling a canard airplane to land on runway 36R not 36L. The pilot stated he began to look for the canard airplane which took his attention off the lead airplane resulting in a decrease of the separation between the airplanes. He stated he got within 10 ft of the lead airplane's right wing at which time he reduced the engine power and pitched up to slow his airspeed. The pilot stated that was then directly behind the lead airplane and below his altitude, when he encountered the lead airplane's wake turbulence and prop wash, and his airplane banked "hard to the right". He corrected by banking to the left, but must have had back pressure on the stick and the airplane stalled. The pilot stated he was about 150 ft above the ground when the loss of control initially occurred. Witnesses reported the airplane was low and slow as it approached the runway. They stated it stalled, rolled left, and descended to impact with the terrain. A GoPro camera was located amongst the wreckage. The 128GB Micro SD card was retrieved from the camera and downloaded by the National Transportation Safety Board (NTSB) Vehicle Recorder Laboratory. It was determined that the camera was mounted on the left wing. A summary of the video was prepared and is attached to this report. The lead airplane was visible in front of the accident airplane as they approached the airport. At one point while the airplanes were descending and approaching the airport, the accident airplane was about the same altitude as the lead airplane. Both airplanes then made a left turn [onto base leg] at which time at least two other airplanes were visible in the distance ahead of the lead airplane. At this point the lead airplane was below the altitude of the accident airplane. Both airplanes then made another left turn onto final approach. About 27 seconds after the accident airplane was established on final approach, the distance between the accident airplane and the lead airplane began to reduce. Other than the lead airplane, no other flying airplanes were visible on approach to either runways 36L or 36R. The distance between the two airplanes continued to reduce. The lead airplane was at or below the attitude of the accident airplane until the accident airplane entered a left bank and began to descend. The left bank continued to increase such that the airplane was nearly inverted as it descended to ground impact. The air traffic control audio recording was reviewed by the NTSB Investigator-in-Charge. At 03:00 [lapsed recording time, minutes (MM): seconds (SS)], the controller cleared a canard airplane to land on runway 36L. About 31 seconds later, the controller changed the canard's landing runway to 36R. At 04:04, a second canard pilot requested landing on runway 36R and 14 seconds later, it was cleared to land on runway 36R. About 15 seconds later, the controller cleared the accident airplane and his lead airplane to land on runway 36L. At 04:42, the controller instructed the canard airplanes to keep rolling to the end of the runway. At 05:00, the accident is announced over the radio. A damaged SD card from a Garmin GPS was also retrieved from the wreckage and sent to the NTSB Vehicle Recorder Laboratory. The card was cracked through its memory chip which prevented data recovery from the card. The accident airplane was the trailing airplane in a flight of two landing on runway 36L at Experimental Aircraft Association AirVenture when the accident occurred. The pilot reported that, while on final approach, he heard an air traffic control transmission telling a canard airplane to land on runway 36R. Mistaking the transmission for 36L, the pilot stated that he began to look for the canard airplane, which diverted his attention from the lead airplane and resulted in a loss of separation. As he approached the lead airplane's right wing, he reduced the engine power and pitched up to slow his airplane. He stated his airplane banked "hard to the right;" he corrected by banking to the left, which, combined with the airplane's nose-high pitch attitude, resulted in an aerodynamic stall. Although the pilot stated that he was directly behind and below the lead airplane, and encountered the airplane's wake turbulence and prop wash, a GoPro camera mounted on the left wing of the accident airplane showed that the airplane remained behind and above the lead airplane; therefore, it is unlikely that the accident airplane encountered wake turbulence. The GoPro footage was consistent with the accident airplane slowing then subsequently experiencing an aerodynamic stall. It is likely that the pilot slowed the airplane excessively as he attempted to maintain separation and exceeded the airplane's critical angle of attack. 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-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Not attained/maintained - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Not attained/maintained - C
Verbatim from NTSB's published report. Source file
NTSB_2016_CEN16LA283.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 (stall, loss of control, wake turbulence, turbulence). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2019 · Conference Paper
Aircraft wake turbulence minimization by aerodynamic means
The paper reviews NASA's efforts on wake vortex turbulence minimization by aerodynamic design or retrofit modifications to large transport aircraft.
- NASA NTRS 2019 · Conference Paper
Wake Turbulence Mitigation for Arrivals (WTMA)
The preliminary Wake Turbulence Mitigation for Arrivals (WTMA) concept of operations is described in this paper. The WTMA concept provides further detail to work initiated by the Wake Vortex Avoidance…
- NASA NTRS 2019 · Conference Paper
Aircraft wake turbulence avoidance
Aircraft wake turbulence /trailing vortex systems/ avoidance during flight, describing procedures for pilots and tower operators
- NASA NTRS 2019 · Conference Paper
Aircraft wake turbulence progress and plans
Aircraft wake turbulence and trailing vortices, investigating physical characteristics, hazard potential and avoidance techniques
- SKYbrary (Eurocontrol) 2023 · SKYbrary article
Wake Vortex Turbulence — SKYbrary Knowledge Base
SKYbrary wake vortex turbulence comprehensive article — generation mechanics, dissipation factors, separation standards (ICAO LIGHT/MEDIUM/HEAVY/SUPER + recategorisation RECAT-EU).
- NTSB Aircraft Accident Reports 2021 · Accident report
Crash of Atlas Air Flight 3591, Boeing 767-300 (N1217A)
Atlas Air 3591 crashed into Trinity Bay, Texas, February 23, 2019. Investigation of the in-flight loss-of-control crash of Atlas Air 3591 into Trinity Bay, Texas.
Browse the full corpus — academia portal ↗