FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14FA072 · Biesemeier David I SMYTH SIDEWINDER

27 Nov 2013 · Boulder, CO, United States

Biesemeier David I SMYTH SIDEWINDER · Accident: part(s) separation from aircraft while maneuvering

From Rocky Mountain Metropolitan Airport (BJC) to Northern Colorado Regional Airport (FNL)

Report a problem

Event

NTSB case
CEN14FA072
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
1 · 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

Biesemeier David I SMYTH SIDEWINDER

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
N3786A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Rocky Mountain Metropolitan Airport (BJC), Broomfield, COTo Northern Colorado Regional Airport (FNL), Loveland, CO
Aircraft age
About 32 years (built 1981)
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
Maneuvering
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
Part(s) separation from aircraft
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft structures
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Radar data showed that, during the first 15 minutes of the cross-country flight, the experimental, amateur-built, airplane had a normal departure and climbout. However, the airplane then suddenly turned and rapidly descended. A witness reported that he heard a loud sound, looked up, and saw the airplane falling out of the sky. Another witness reported seeing flocks of migrating birds in the area about the time of the accident. No radio calls or distress transmissions were received from the pilot. The airplane's left wing was found about 1,156 ft from the main wreckage. Examination of the engine and flight controls did not reveal any mechanical anomalies that might have contributed to the accident.

Examination of the left wing revealed no evidence of preexisting conditions that would have contributed to its separation. The wing's left lower spar cap was fractured about 8 inches outboard of the attachment point through the two rivet holes immediately outboard of the wing-to-fuselage fittings. There was no obvious deformation of the lower spar cap members in the fracture area. The upper spar cap members were fractured between 10 and 12 inches outboard of the attachment point with significant S-type bending of the members in the fracture area. The upper shear bolt remained intact and installed, but the lug portion of the fuselage fitting was fractured. The fracture faces on the upper and lower spar cap members all had a dull, angled, grainy appearance consistent with overstress separation. The lack of deformation of the lower spar cap members, the bending deformation of the upper spar cap members, and the appearance of the fracture faces on the individual members are consistent with a tension overload failure of the lower spar cap and compression overload failure of the upper spar cap. The evidence is consistent with the separation of the left wing due to a positive overload condition.

Although flocks of migrating birds were seen in the area about the time of the accident, no evidence was found indicating that an in-flight bird strike occurred. However, it is likely that the pilot made an abrupt maneuver, possibly to avoid birds, which resulted in excessive g forces on the wing structure and led to its separation. An autopsy of the pilot did not reveal any medical conditions that might have contributed to the accident.

Probable cause

The pilot’s abrupt maneuver, which exceeded the structural limits of the left wing and resulted in its in-flight separation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14FA072
Event ID
20131202X13540
Case number
CEN14FA072
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, coordinates. 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: 88d363321e7b72f2cd255dc35e9e14c6fa746c96d1756bbd403171ca6c3f6a60; retrieved 2026-09-14T16:08:07.341Z.