FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC10FA022 · Antares MA-32

13 Mar 2010 · Chugiak, AK, United States

Antares MA-32 · Accident: loss of control in flight while maneuvering

From Birchwood Airport (PABV) to Birchwood Airport (PABV)

Report a problem

Event

NTSB case
ANC10FA022
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
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
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

Antares MA-32

Aircraft type
Antares MA-32
Category
Weight-Shift
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
N7JQ
Onboard fatalities
Unknown
Route
From Birchwood Airport (PABV), Birchwood, AKTo Birchwood Airport (PABV), Birchwood, AK
Aircraft age
Not recorded
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
Maneuvering
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
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

The pilot's decision to pitch the aircraft excessively during a steep climbing maneuver, resulting in a loss of control and an aerodynamic tumble.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC10FA022
Event ID
20100314X03848
Case number
ANC10FA022
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2010-03-14.
  • API snapshot SHA-256: 4d48fc2e9c63dd4fd8ad3696cbb6a1ef34b40ee3eac5595c33f94c7727adf595; retrieved 2026-09-13T20:42:51.568Z.