Cessna 150G accident near Ellicott, Colorado, March 21, 2026
On March 21, 2026 at about 4:23 pm local time, a Cessna 150G, registered N6305S, was substantially damaged in an accident during approach near Ellicott, Colorado (Colorado Springs East airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 21, 2026 · about 4:23 pm local time
- Place
- Ellicott, Colorado · Colorado Springs East · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 150G · all 150Gs on the register
- Registration
- N6305S · registry record · serial 15067105
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On March 21, 2026, about 1023 mountain daylight time, a Cessna 150G airplane, N6305S, was substantially damaged when it was involved in an accident near Ellicott, Colorado. The pilot sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he recalled completing a preflight inspection, a before takeoff engine run-up, and taxing onto the runway for takeoff. He did not recall any portion of the accident sequence. A witness stated that the pilot intended to conduct some takeoffs and landings for currency. The pilot departed toward the south, and the takeoff appeared normal. The airplane went out of sight behind a hangar. However, when he regained sight of it, the airplane was on an easterly heading and in an approximate 60° left bank. The airplane subsequently impacted the ground near wings level. It came to rest on a northeast heading about 100 ft before the departure end of the runway and about 500 ft left of the centerline. The airplane sustained damage to the fuselage, empennage, and both wings. Airframe and engine examinations are planned. Figure 1 – Airplane at accident site (Police department photo)
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Medical event during approach defining event
The aircraft
- Seats: 2
- Landing gear: fixed
The flight
- Departed from: CO4 Ellicott CO at 10:20 pm
- Destination: CO4 Ellicott CO
- Flight plan: none
- Runway 17R, 4,500 ft by 42 ft
Weather at the time
- Light: daylight
- Wind: from 160° at 5 knots, gusting 2
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 43°F (6°C), dew point 28°F (-2°C)
- Altimeter: 30.22 inHg
- Observation at 10:15 am from KFLY, 9 miles away
Weather report (METAR): METAR KFLY 231615Z AUTO 16005KT 10SM CLR 06/M02 A3022
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.