ERA22LA274 · Cessna 172 M
Franklin Air Services Cessna 172 M · Accident: low altitude operation/event while maneuvering
From Asheville Regional Airport (AVL) to an unrecorded destination
Event
- NTSB case
- ERA22LA274
- 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
- Event fatalities
- Unknown
- 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
Cessna 172 M
- Aircraft type
- Cessna 172
- 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
- N5064H
- Operator
- Franklin Air Services
- Onboard fatalities
- Unknown
- Route
- From Asheville Regional Airport (AVL), Asheville, NCTo not recorded
- Aircraft age
- About 47 years (built 1975)
- 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 · low-altitude flying
- 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
- Low altitude operation/event
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and two passengers were flying at low altitudes over a camp and dropping candy from the airplane. The pilot recalled that the airplane was “a couple hundred feet” above the trees in slow flight; the next thing that the pilot remembered was waking up in a hospital. During the flight, one of the passengers commented to the pilot that the airplane was getting close to the treetops and that he needed to apply power and pull up. The pilot stated something similar to, “I’m working on it.” The passenger recalled that the airplane hit trees and that he woke up next to the airplane. He also stated that the engine was operating normally.
Postaccident examination of the airplane revealed no evidence of mechanical malfunctions or anomalies that would have precluded normal operation. An onboard image recording from a camera found at the accident site revealed that the airplane was maneuvering at a low altitude and high bank angles until the airplane impacted terrain.
Given the passenger’s recollections and the onboard image recording evidence, the pilot allowed the airplane to sink below the level of the treetops while conducting high bank angles at a low altitude.
Probable cause
The pilot’s failure to maintain altitude while maneuvering the airplane at a low altitude, which resulted in impact with trees and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA274
- Event ID
- 20220620105281
- Case number
- ERA22LA274
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
- 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, cause areas. 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: d850aea18e4a12b76cf291ff93fff807657970a0449c403725851167b6687c45; retrieved 2026-09-16T15:20:43.828Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: departure. Misspelled city name; AVL is Asheville, North Carolina.