ERA18LA096 · Piper PA 28 140
Piper PA 28 140 · Accident: collision during takeoff/landing on approach
From Massey Ranch Airpark (X50) to Massey Ranch Airpark (X50)
Event
- NTSB case
- ERA18LA096
- 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
Piper PA 28 140
- Aircraft type
- Piper PA-28
- 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
- N6764W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Massey Ranch Airpark (X50), Edgewater, FLTo Massey Ranch Airpark (X50), Edgewater, FL
- Aircraft age
- About 53 years (built 1965)
- 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
- Approach · VFR pattern final
- 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
- Collision during takeoff/landing
- 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
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor and a student pilot were practicing pattern work at the airport. Due to their injuries, they did not recall any events before the accident. A witness reported that during a landing just before the accident, the airplane was "low" on the final leg of the traffic pattern, appeared to have increased engine power to clear the tree line, and then continued on the approach. The witness did not observe the accident sequence. Examination of the accident site and wreckage revealed that the airplane struck trees before impacting the ground about 750 ft before the runway. Examination of the airplane revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal engine operation. Given the available information, it is likely that the flight instructor allowed the airplane to descend below a normal approach path to the runway, as seen on a previous approach, which resulted in the collision with trees and terrain.
Probable cause
The flight instructor's failure to maintain the appropriate glidepath to the runway, which resulted in a collision with trees and terrain during final approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA18LA096
- Event ID
- 20180306X14210
- Case number
- ERA18LA096
- 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. 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: b979841813aa8b4a40f0feb403d9ef167d7b191ae4a91e18f8ebbe43e03309d8; retrieved 2026-09-16T06:34:51.398Z.