DEN93LA069 · Irving Siewert OSPREY GP-4 OSPREY GP-
Irving Siewert OSPREY GP-4 OSPREY GP- · Accident: airframe, component or system failure en route
Event
- NTSB case
- DEN93LA069
- 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
- 0
- 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
Irving Siewert OSPREY GP-4 OSPREY GP-
- Aircraft type
- Irving Siewert OSPREY GP-4
- 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
- N85Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- Not recorded
- 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
- En route · cruise
- First occurrenceThe 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
- Airframe, component or system failure
- 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
- Destroyed
Cause areas
- Manufacturer › Material inadequate, improper
Approximate · Estimated position: the centre of Cañon City, CO, the place the record names. Not the accident site.
NTSB narrative
WHILE ON A LOCAL AREA FLIGHT, THE AIRCRAFT BROKE UP IN FLIGHT WITH THE CANOPY AND HORIZONTAL/VERTICAL STABILIZER SEPARATING FROM THE AIRCRAFT. REVIEW OF DESIGN SPECIFICATION PROVIDED INFORMATION THAT THE PILOT/BUILDER HAD USED A NON STANDARD CANOPY LATCH AND CONSTRUCTED THE WINDSHIELD BOW FROM FIBERGLASS VICE THE ALUMINUM MATERIAL REQUIRED. THE CANOPY CAME OFF IN FLIGHT AND STRUCK THE LEFT HORIZONTAL STABILIZER CAUSING THE HORIZONTAL AND VERTICAL STABILIZER TO SEPARATE FROM THE AIRCRAFT.
Probable cause
FAILURE BY THE PILOT/BUILDER TO FOLLOW CONSTRUCTION SPECIFICATIONS AND THE USE OF IMPROPER MATERIALS DURING CONSTRUCTION OF THE AIRCRAFT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN93LA069
- Event ID
- 20001211X12599
- Case number
- DEN93LA069
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 320b5b5a5ca9f28537a86517ce2e8b75b948dd6f240aa9eea2a004b0b987c845; retrieved 2026-09-21T00:30:46.418Z.