ERA14CA234 · SAM R Peachey JUST AIRCRAFT HIGHLA
SAM R Peachey JUST AIRCRAFT HIGHLA · Accident: loss of control in flight while maneuvering
From Franklin County Regional Airport (N68) to Franklin County Regional Airport (N68)
Event
- NTSB case
- ERA14CA234
- 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
SAM R Peachey JUST AIRCRAFT HIGHLA
- Aircraft type
- Sam R Peachey JUST AIRCRAFT HIGHLA
- 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
- N209SP
- Operator
- Peachey Sam R
- Onboard fatalities
- Unknown
- Route
- From Franklin County Regional Airport (N68), Chambersburg, PATo Franklin County Regional Airport (N68), Chambersburg, PA
- Aircraft age
- About 3 years (built 2011)
- 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
- 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 › 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
According to the pilot, he was flying about 500 feet above the ground, dropping candy to children as part of a church outing. He encountered a "rotor" wind off the nearby mountain and when he initiated a turn, the wing stalled. He lost control of the airplane and crashed near a church camp. The airplane came to rest, inverted. An inspector from the Federal Aviation Administration examined the airplane and confirmed substantial damage to the fuselage, wings, and empennage. The pilot reported no pre-impact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's failure to maintain adequate airspeed during low altitude maneuvering.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA234
- Event ID
- 20140511X11126
- Case number
- ERA14CA234
- 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: c548ebd3f651f73ccc5a07129f1cc339b3bfa31560ec804a384036bc06da4ded; retrieved 2026-09-15T23:36:37.497Z.