Amateur-built GLASTAR accident near Canon City, Colorado, June 6, 2011
On June 6, 2011 at about 4:30 pm local time, a amateur-built GLASTAR, registered N238W, was substantially damaged in an accident during approach (VFR pattern base) near Canon City, Colorado (Fremont County Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A loss of engine power due to an overheated engine as a result of a malfunction of the modified engine cooling system, necessitating a forced landing on unsuitable terrain.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 6, 2011 · about 4:30 pm local time
- Place
- Canon City, Colorado · Fremont County Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built GLASTAR
- Registration
- N238W · no longer on the register · serial 05110
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot said the flight was made to test a new cooling modification on the engine. The engine soon began overheating and seized when the airplane was on the base leg of the traffic pattern, forcing the pilot to land short of the runway in loose dirt. The impact crushed the outboard portion of the left wing and buckled the upper skin of the right wing.
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
- Sys/Comp malf/fail (non-power) during maneuvering
- Loss of engine power (total) during approach (VFR pattern base) defining event
- Off-field or emergency landing during emergency descent
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Failure
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng liquid cooling › Malfunction
- Environmental issues › Physical environment › Runway/land/takeoff/taxi surfa › Soft › Contributed to outcome
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 521 hours in all; 2 in this make and model; 1 in the last 90 days; 1 in the last 30 days; 427 as pilot in command
- Last flight review: January 15, 2008
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2 hours
- Last inspection: inspection type not recorded, June 1, 2011
- Maximum gross weight: 1,950 lb
- Seats: 2
- Landing gear: fixed
- Engine: Subaru ALL MDLS A/B (piston); 0 hours total
The flight
- Departed from: 1V6 Canon City CO at 4:15 pm
- Destination: 1V6 Canon City CO
- Flight plan: none
- Runway 29, 5,400 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 110° at 29 knots, gusting 35
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
- Altimeter: 30.04 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket 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.