ERA17CA068 · Beech A36 UNDESIGNAT
Beech A36 UNDESIGNAT · Accident: loss of control in flight on approach
From Spruce Creek Airport (7FL6) to Spruce Creek Airport (7FL6)
Event
- NTSB case
- ERA17CA068
- 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
Beech A36 UNDESIGNAT
- Aircraft type
- Beechcraft 36
- 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
- N776WM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Spruce Creek Airport (7FL6), New Smyrna Beach, FLTo Spruce Creek Airport (7FL6), New Smyrna Beach, FL
- Aircraft age
- About 33 years (built 1983)
- 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
- Approach · VFR pattern downwind
- 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17CA068
- Event ID
- 20161212X35012
- Case number
- ERA17CA068
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 75e79e9ddbe87ac52fd8498d470aeeb407dabf21c7c6b5c9a2529586fdc7094e; retrieved 2026-09-16T04:53:21.121Z.