FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25FA366 · Beech P35

5 Sept 2025 · Englewood, CO, United States

Beech P35 · Accident: loss of control in flight on approach

From Centennial Airport (KAPA) to an unrecorded destination

Report a problem

Event

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

Beech P35

Aircraft type
Beechcraft 35
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
N463T
Onboard fatalities
Unknown
Route
From Centennial Airport (KAPA), Englewood, COTo not recorded
Aircraft age
About 62 years (built 1963)
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
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 September 5, 2025, about 0623 mountain daylight time, a Beech P35 airplane, N463T, was destroyed when it was involved in an accident near Englewood, Colorado. The pilot receiving instruction and flight instructor were both fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. The pilot receiving instruction was receiving familiarization training as he planned to purchase a similar airplane. ADS-B data for the accident flight showed the airplane departed from runway 35R at the Centennial Airport (KAPA), Englewood, Colorado, about 0543, remained in the traffic pattern. and performed several landings. Archived tower audio recordings captured that after performing a stop and go landing to runway 17L, one of the pilots said they were “on the roll”. This was the last recorded radio transmission from the airplane. When the tower controller cleared them “the option” no response was recorded. The tower controller later requested the pilots “ident” if they heard the transmission and the tower controller replied, “ident observed.” No distress calls were recorded from either pilot. ADS-B data showed at 0622:15, the airplane stopped a climb and began to descend. At 0622:43, data recorded the airplane’s ident. The descent continued until the last recorded point of 0623:05 when the airplane was about 5,900 ft mean sea level, and 77 knots groundspeed. A firefighter located about 1.5 miles south of the accident site heard the airplane fly overhead and heard the engine stop completely. A woman who lives in a neighborhood south of the airport was walking when she saw the airplane flying on a different flight path and lower than she was used to normally seeing. She heard the engine go silent and looked up to observe the airplane in a “hard” left bank towards the airport and in a descent. The airplane appeared normal, and she thought the airplane was conducting training. Cameras from businesses around the accident site captured low-resolution video which showed the airplane descending in a left bank. Just before ground impact, the airplane banked right.

Figure 1 ADS-B Data Plots with Accident Site (triangle) The airplane impacted a paved driveway of an industrial facility. Initial impact points were scrapes on the asphalt aligned on a 280° heading towards the accident site. The main wreckage consisted of a majority of the airplane. Portions of the right wing were scattered to the south of the debris path. The left wing was fractured near the wing root and was found folded aft. The remainder of the airplane remained in its expected orientation. Signatures were consistent with the airplane colliding with several concrete pole barriers in front of a generator unit before coming to rest on a 060°heading. Flight control continuity was established from the cockpit to the aileron bellcranks and ruddervators. The dual control wheel chain was observed with the aileron yoke chain around its sprocket. The landing gear and flaps were both found retracted. The propeller remained attached to the engine which was displaced aft into the cockpit area. The airplane was retained for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record CEN25FA366
Event ID
20250905200946
Case number
CEN25FA366
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: fbe3301df072e5948ececfd92f5b7e5cca433527caa244164cf4e99c3e564893; retrieved 2026-09-15T09:08:45.054Z.