CEN25FA178 · Beech 95-B55 (T42A)
Beech 95-B55 (T42A) · Accident: loss of control in flight on approach
From Rocky Mountain Metropolitan Airport (BJC) to Sidney, NE
Event
- NTSB case
- CEN25FA178
- 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
- Ongoing
- API-reported fatalities
- 2 · 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 95-B55 (T42A)
- Aircraft type
- Beechcraft 55
- 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
- N4321Z
- Operator
- Cedocs
- Onboard fatalities
- Unknown
- Route
- From Rocky Mountain Metropolitan Airport (BJC), Broomfield, COTo Sidney, NE
- Aircraft age
- About 53 years (built 1972)
- 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
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On May 17, 2025, about 1003 mountain daylight time, a Beechcraft 95-B55, was destroyed when it was involved in an accident near Broomfield, Colorado. The pilot and pilot-rated passenger sustained fatal injuries. The flight was being operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to family members, the owner was providing a cross-country familiarity flight to the pilot-rated passenger who had recently purchased a similar airplane. Preliminary air traffic control (ATC) radar data showed the airplane depart runway 30R from the Rocky Mountain Metro Airport (BJC), Broomfield, about 1000. Shortly after rotation, the pilot made a radio call to the BJC control tower stating, “we had a door pop, we need to come back around.” ATC subsequently replied that the pilot could make “right closed traffic for 30R” along with asking the pilot are “you going to climb?” Airport surveillance camera footage and radar data showed the airplane stopped its initial climb at 6,024 ft mean sea level (msl), about 400 ft above ground level, shortly after passing the departure end of runway 30R. ATC made numerous attempts to elicit a response from the pilot stating that they were cleared to land runway 30R and further cleared the pilot to land the airplane on any runway. The airplane entered the right traffic pattern for runway 30R, as instructed, and started a continuous slow descent. During the right crosswind to downwind turn, the airplane slowed from 94 knots (kts) groundspeed at 1002:12 to 81 kts about 15 seconds later. At 1002:49, surveillance camera video from a bus stop along U.S. Route 36, located near the right downwind traffic pattern leg, captured the airplane with the landing gear extended entering a left bank that increased in roll rate until the airplane was in an inverted left wing down and nose low dive at 1002:53. The surveillance video shows what appears to be an open door, consistent with the pilot’s report to ATC (see Figure 1).
Figure 1. Surveillance camera video still image.
The accident site was in a flat open field about 1.5 nautical miles north of runway 30R. Impact marks and debris were consistent with the airplane impacting the terrain in an estimated 90° left bank and nose down attitude. During the impact, the airplane rotated counterclockwise 180° opposite the direction of travel and came to rest upright. The debris field was about 85 ft in length with evidence of a postaccident fire.
The main cabin door was separated from the airplane, located on the left side of the debris path, and the door handle was found in the open position (see Figure 2). The rear sloped latch, lower pin, and upper claw latch were found in the locked position.
Figure 2. Interior side of main cabin door
The components of the cabin baggage door thumb latch were located in the fuselage debris, and the latch was found in the closed and locked position. The nose baggage door could not be identified due to impact fragmentation of the forward fuselage. Flight control continuity was established from all flight control surfaces to their respective controls.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record CEN25FA178
- Event ID
- 20250517200166
- Case number
- CEN25FA178
- 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: d3a16c93860935cbdc278bb52e8462a3eba1c70439fcb1dba2acb21412a16d11; retrieved 2026-09-15T09:05:02.910Z.