Amateur-built GLASTAR accident near Arlington, Washington, July 5, 2009
On July 5, 2009, a amateur-built GLASTAR, registered N432P, was substantially damaged in an accident during initial climb near Arlington, Washington (Arlington Municipal 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 total loss of engine power due to fuel starvation as a result of the pilot's failure to select the fullest tank prior to takeoff.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 5, 2009
- Place
- Arlington, Washington · Arlington Municipal 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
- N432P · registry record · serial 5386
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that the purpose of the flight was to practice touch-and-go landings. During the takeoff portion of a touch-and-go, about midway down the runway, the engine lost power. The pilot initiated a gentle left turn towards a vacant taxiway to initiate a forced landing. The pilot landed hard just short of the taxiway. The left wing was wrinkled, and the nose wheel and left main landing gear collapsed. The pilot stated that he had the incorrect fuel tank selected, and "the engine lost power due to fuel starvation." He also stated that prior to takeoff, one fuel tank had "little to no fuel" and "the other fuel tank was about half full." The pilot reported no mechanical anomalies with the engine or airframe prior to the accident.
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
- Fuel starvation during initial climb defining event
- Loss of engine power (total) during initial climb
- Off-field or emergency landing during emergency descent
The NTSB's findings
- cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid management
- cause Personnel issues › Task performance › Use of equip/info › (general) › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 200 hours in all; 138 in this make and model; 7 in the last 90 days; 3 in the last 30 days; 200 as pilot in command
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 138 hours
- Last inspection: annual inspection, March 20, 2009; 6 hours since
- Seats: 2
- Landing gear: fixed
- Engine: Ama/Expr Subaru (piston); 0 hours total
The flight
- Departed from: KAWO Arlington WA
- Destination: KAWO Arlington WA
- Flight plan: not recorded
- Runway 34, 5,332 ft by 100 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 64°F (18°C), dew point 0°F (-18°C)
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.