NTSB CAROL · Event
Event ERA17CA068
Aircraft involved
Probable cause & findings
The pilot's inappropriate response to an emergency exit window opening in flight, which resulted in a loss of control, precautionary off-airport landing, and subsequent impact with trees. Contributing to the accident was the pilot's improper repair of the emergency exit window before the flight.
Factual narrative
During a winter flight, passengers reported that cold air was entering the airplane from the left side of the passenger cabin. Afterwards, the pilot examined the area and discovered that there was a small gap under the emergency exit window that was allowing air to enter the cabin from outside the airplane. He opened the window and examined the rubber seal which was intact. He could not tell though, if it was compressed or thinner than normal. He then closed and latched the window and inspected the latch with a flashlight to make sure it was latched. Since he was going to fly back to his home airport in similar winter conditions on the next flight, He took several rolled-up paper towels and placed them between the trim and the window to try and keep the cold air out, and placed a strip of blue painters tape on the outside of the lower portion of the window to further reduce the entry of cold air. Since it was a beautiful day, he decided to fly the airplane once around the traffic pattern before fueling up for his return flight. After takeoff while on the downwind leg of the traffic pattern at 800 feet, he suddenly heard a "whoosh" behind his seat. Instead of landing, and then checking to see what happened, he instead checked for other traffic, turned on the autopilot, in heading and altitude mode, then reached around behind him to shut and latch the window which had opened 2 to 3 inches. Moments later, after turning back around to his normal seated position, he then heard a loud "pop" and turned around to find that the window had now opened completely. Since he was afraid it would come off the airplane and strike the tail, he reached back once again and pulled the window back down. The pilot advised that he must have "bumped" the autopilot off while he was doing this, since when he looked forward to check for traffic, he noticed that the airplane was approaching the ground. He then banked left and right to determine his location and spot any obstacles, raised the nose, and added power to climb. He then noticed that there were powerlines slightly higher than his altitude directly in front of him, and rather than risk a possible stall close to the ground by pulling back suddenly, he lowered the nose and "put" the airplane on the ground. At this point the airplane was approaching the edge of a field bordered by trees, so he pointed the nose of the airplane between trees. The airplane then struck the trees, and a fire ensued, resulting in substantial damage to the airframe. Examination of the emergency exit window by a Federal Aviation Administration inspector revealed that the paper towels the pilot inserted in the gap between the window and the airframe were interfering with the window's latching mechanism. Passengers reported that, during a winter flight, cold air was entering the airplane from the left side of the passenger cabin. Afterward, the pilot examined the area and discovered that there was a small gap under the emergency exit window that was allowing air to enter the cabin from outside the airplane. He opened the window and examined the rubber seal, which was intact. However, he could not tell if it was compressed or thinner than normal. He then closed and latched the window and inspected the latch with a flashlight to make sure it was latched. Because he was going to fly back to his home airport in similar winter conditions on the next flight, he took several rolled-up paper towels and placed them between the trim and the window to try and keep the cold air out and placed a strip of blue painter's tape on the outside of the lower portion of the window to further reduce the entry of cold air. He decided to fly the airplane once around the traffic pattern before fueling up for his return flight. After takeoff and while on the downwind leg of the traffic pattern at 800 ft, he suddenly heard a "whoosh" behind his seat. Instead of landing and checking to see what happened, he checked for other traffic, turned on the autopilot, in heading and altitude mode, then reached around behind him to shut and latch the window, which had opened 2 to 3 inches. Seconds later, after turning back around to his normal seated position, he heard a loud "pop" and turned around and saw that the window had opened completely. Given that he was afraid it would come off the airplane and strike the tail, he reached back again and pulled the window down. The pilot reported that he must have "bumped" the autopilot off while he was doing this, because when he looked forward to check for traffic, he noticed that the airplane was approaching the ground. He then banked left and right to determine his location and spot any obstacles, raised the nose, and added power to climb. He then noticed that there were power lines slightly higher than his altitude directly in front of him, and rather than risk a possible stall close to the ground by pulling back suddenly, he lowered the nose and "put" the airplane on the ground. The airplane then struck trees, and a fire ensued, which resulted in substantial damage to the airframe. Examination of the emergency exit window by a Federal Aviation Administration inspector revealed that the paper towels the pilot inserted in the gap between the window and the airframe were interfering with the window's latching mechanism. 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-Action/decision-Action-Incorrect action performance-Pilot - C
- C Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- F Personnel issues-Task performance-Maintenance-Repair-Pilot - F
- F Aircraft-Aircraft structures-Doors-Emergency exit-Incorrect service/maintenance - F
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Altitude-Not attained/maintained
- — Environmental issues-Physical environment-Object/animal/substance-Tree(s)-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2016_ERA17CA068.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, autopilot). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Semantic Scholar 2016 · Article (Interacción)
Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report
Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- arXiv 2026 · arXiv preprint
Robust Adaptive Sliding-Mode Control for Damaged Fixed-Wing UAVs
Many unmanned aerial vehicles (UAVs) can remain aerodynamically flyable after sustaining structural or control surface damage, yet insufficient robustness in conventional autopilots often leads to mis…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- arXiv 2025 · arXiv preprint
ROSflight 2.0: Lean ROS 2-Based Autopilot for Unmanned Aerial Vehicles
ROSflight is a lean, open-source autopilot ecosystem for unmanned aerial vehicles (UAVs). Designed by researchers for researchers, it is built to lower the barrier to entry to UAV research and acceler…
Browse the full corpus — academia portal ↗