FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA18CA544 · Halladay ROY LOCKHEED T-33

9 Sept 2018 · Denver, CO, United States

T-33 Aviation Halladay ROY LOCKHEED T-33 · Accident: part(s) separation from aircraft during landing

From Centennial Airport (APA) to Rocky Mountain Metropolitan Airport (BJC)

Report a problem

Event

NTSB case
GAA18CA544
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

Halladay ROY LOCKHEED T-33

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
N514RH
Onboard fatalities
Unknown
Route
From Centennial Airport (APA), Denver, COTo Rocky Mountain Metropolitan Airport (BJC), Denver, CO
Aircraft age
About 18 years (built 2000)
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
Landing · landing roll
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
Substantial

Cause areas

  • Aircraft › Aircraft structures
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that, upon landing, he activated the canopy motor to open the canopy about 2 inches, but the canopy continued to open, separated from the airframe, and struck the empennage. He added that it was standard procedure upon landing to open the canopy slightly to aid in slowing the airplane and egress in a runway excursion event.

The airplane sustained substantial damage to the empennage.

The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot added that the emergency canopy release, which anchors the canopy to the airframe when the canopy motor was turned on, was inadvertently released during the flight.

Probable cause

The pilot's failure to verify that the emergency canopy release was in the correct position when opening the canopy during landing, which resulted in the canopy separating from the airplane and subsequently impacting the empennage.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA544
Event ID
20180910X84852
Case number
GAA18CA544
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: 37811c6092543b0165ae92512932d3f76007edb28f8709b0d226424aff269472; retrieved 2026-09-16T08:13:57.508Z.