ANC09FA003 · Antonovich Anton B CHALLENGER II
Antonovich Anton B CHALLENGER II · Accident: loss of control in flight while maneuvering
From BVC · Birchwood, AK to BVC · Birchwood, AK
Event
- NTSB case
- ANC09FA003
- 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
Antonovich Anton B CHALLENGER II
- Aircraft type
- Antonovich Anton CHALLENGER
- 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
- N7511J
- Operator
- Richard H. Roiland · private individual
- Onboard fatalities
- Unknown
- Route
- From BVC · Birchwood, AKTo BVC · 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
- 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
- Aircraft › Aircraft oper/perf/capability
- 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 non-certificated pilot departed on a Title 14, CFR Part 91, local area personal flight in an experimental light sport homebuilt airplane. A witness reported seeing the airplane flying about 100 feet above trees before the engine noise increased, and the nose pitched down. The airplane subsequently descended nose first into dense woods. The pilot’s flight instructor reported to the NTSB that he had given the pilot 19.2 hours of flight instruction, but the pilot had not progressed to a point where he could endorse him for a solo flight. He said that the pilot routinely struggled with pitch control during takeoff, landing, or when engine power was increased or decreased. Examination of the airplane did not disclose any preimpact mechanical malfunction. Given the lack of mechanical deficiencies with the airplane's engine or flight controls, in conjunction with the witness and the flight instructor’s statements, it is likely the pilot failed to adequately maintain control of the airplane while maneuvering.
Probable cause
The pilot’s failure to maintain control of the airplane while maneuvering, resulting in an in-flight collision with trees. Contributing to the accident was the pilot's lack of experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC09FA003
- Event ID
- 20081008X82640
- Case number
- ANC09FA003
- 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: 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: 3019ae530dc3e1b2558480eaec203024254f0594eb42719a66fddcf7af7a82da; retrieved 2026-09-13T19:32:36.035Z.