FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC06CA123 · Frisby CH801

27 Aug 2006 · Palmer, AK, United States

Frisby CH801 · Accident: loss of control in flight during initial climb

From Palmer, AK to Warren "Bud" Woods Palmer Municipal Airport (PAQ)

Report a problem

Event

NTSB case
ANC06CA123
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
0 · 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

Frisby CH801

Aircraft type
Frisby CH801
Category
Airplane
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
N801ZA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Palmer, AKTo Warren "Bud" Woods Palmer Municipal Airport (PAQ), Palmer, 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
Initial climb
First occurrenceThe 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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Pilot in command › Compensation for wind conditions, inadequate

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

NTSB narrative

The commercial certificated pilot was departing from a private airstrip surrounded by trees in a wheel-equipped experimental airplane, during a Title 14, CFR Part 91 personal flight. After becoming airborne, a gust of wind pushed the airplane to the left, and the left wing struck a stand of trees, which pivoted the airplane to the left. The airplane subsequently collided with the ground, and sustained structural damage to the wings, fuselage, and empennage. The pilot noted that there were no preaccident mechanical anomalies with the airplane.

Probable cause

The pilot's inadequate compensation for wind conditions, which resulted in an in-flight collision with trees during takeoff. Factors associated with the accident were wind gusts, and trees bordering the airstrip.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC06CA123
Event ID
20061005X01471
Case number
ANC06CA123
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: c88e21516805164deb5252aa29b9611476ca929180453901b15d44159ff90b60; retrieved 2026-09-21T18:41:36.665Z.