CHI95LA214 · Avid Aircraft FLYER
Avid Aircraft FLYER · Accident: loss of control in flight during initial climb
Event
- NTSB case
- CHI95LA214
- 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
- 0
- 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
Avid Aircraft FLYER
- Aircraft type
- Avid FLYER
- 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
- N8031M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- 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 › Operation with known deficiencies in equipment, intentional
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT HE HAD FLOWN THE AIRCRAFT TWICE IN NOVEMBER 1994, AND THAT THE AILERONS HAD BEEN 'SLUGGISH' AND 'SPONGY.' HE HAD NOT FLOWN AGAIN UNTIL THE DAY OF THE ACCIDENT. HE DEPARTED HIS PRIVATE AIRSTRIP AND 'WIGGLED' THE WINGS PASSING 50 FEET. HE FELT THE SAME SLUGGISHNESS THAT HE FELT THE PREVIOUS NOVEMBER. AT 200 FEET HE REDUCED POWER AND STARTED A 15 DEGREE ANGLE OF BANK TURN. HE TRIED LEVELING THE WINGS BUT THE AILERONS WERE UNRESPONSIVE AND THE AIRPLANE CONTINUED TO ROLL. AT 50 FEET HE APPLIED FULL POWER AND RIGHT RUDDER. THE AIRPLANE STRUCK THE GROUND WITH THE WINGS NEARLY LEVEL. THE PILOT STATED THAT HE MIGHT HAVE REDUCED TOO MUCH POWER AND GOT TOO SLOW, STALLING THE AIRPLANE. HE HAD NOT FLOWN RECENTLY. HE ALSO STATED THAT ANOTHER EXPERIENCED PILOT FAMILIAR WITH AN 'AVID FLYER' SHOULD HAVE CHECKED THE FLIGHT CONTROLS BEFORE HE HAD FLOWN THE AIRPLANE AGAIN.
Probable cause
the pilot operating the airplane with known deficiencies. Factors included lack of recent flight experience, inadequate maintenance, and low airspeed.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI95LA214
- Event ID
- 20001207X03890
- Case number
- CHI95LA214
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1995-07-09.
- API snapshot SHA-256: 3088f802f039c73fde4226819d99729622c04141071f1f5e7d6562da192cbb98; retrieved 2026-09-21T22:11:14.868Z.