Antares MA-32 accident near Chugiak, Alaska, March 14, 2010
On March 14, 2010 at about 1:00 am local time, a Antares MA-32 (weight-shift aircraft), registered N7JQ, was substantially damaged in an accident during maneuvering near Chugiak, Alaska. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's decision to pitch the aircraft excessively during a steep climbing maneuver, resulting in a loss of control and an aerodynamic tumble.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 14, 2010 · about 1:00 am local time
- Place
- Chugiak, Alaska · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Antares MA-32
- Registration
- N7JQ · no longer on the register · serial MA32-155
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The solo private pilot was on a personal local flight in a ski-equipped experimental light sport weight-shift-control, pusher aircraft (Trike) under Title 14, CFR Part 91. He died as a result of the accident, and was found about 10 feet from the aircraft. The accident aircraft was found near a railroad track by the crew of a passing train. According to his logbook entries, the pilot had 233 hours of powered flight experience, and logged 4.5 hours of flight in the past 15 months. According to a friend, the accident flight was his first flight of this year. No evidence of a current required aircraft annual condition inspection was discovered. The pilot had replaced the aircraft’s original engine with a more powerful 100 horsepower engine, and it was also equipped with a digital video camera mounted on the forward support strut facing forward. A review of the accident flight video showed the control tube upper support cables moving in and out of the left and right sides of the camera’s field of view. The nose of the aircraft and the single front ski could also be seen in the video. Before the accident, the aircraft was flying at a low altitude over snow-covered flats to the west of the accident site. It made a steep climbing right turn to the east and continued to climb at a very steep angle. The angle of bank approached 90 degrees relative to the horizon, the climb appeared to stop, and the nose fell through the horizon rapidly. A frame-by-frame review showed that prior to the nose falling through the horizon, the wind screen was pushed forward into the cameras field of view, and then to the left, indicating that the aircraft was descending backward. The camera recorded an event consistent with a aerodynamic tumble. During the tumble, the camera mount broke and the camera drifted away and fell alongside the tumbling aircraft, continuing to record the aircraft. The aircraft had been equipped with automotive style lap belts and shoulder harnesses, with plastic push-button receiver type buckles. The pilot's lap belt buckle came apart during the tumble, likely due to the airframe flexing between the shoulder harness mast attachment and the floor mounted lap belt attachment, which placed a tension load on the pilot's lap belt buckle. The camera attained a position below the aircraft, and showed the pilot separate from the aircraft above the treetops. The accident aircraft was originally constructed as a two-place ultralight trainer, and later transitioned to experimental light sport category aircraft. Transitioned aircraft were not subject to the construction standards of ELSA, and therefore there was no standard for occupant restraint systems.
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
- Loss of control in flight during maneuvering defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Pitch control › Capability exceeded
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 233 hours in all
- Last flight review: June 10, 2009
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: frt
- Injury: fatal
The aircraft
- Airframe total time: 259 hours
- Last inspection: condition inspection, September 2, 2007
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 912ULS (piston); 0 hours total
The flight
- Departed from: PABV Birchwood AK
- Destination: PABV Birchwood AK
- Flight plan: not recorded
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 18°F (-8°C), dew point 9°F (-13°C)
- Altimeter: 29.35 inHg
- Observation at 7:56 pm from PAVB, 2 miles away
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.
