ERA10CA090 · Piper PA-38-112
Piper PA-38-112 · Accident: collision during takeoff/landing
From Patillas Airport (X64) to JRV · Ceiba, PR
Event
- NTSB case
- ERA10CA090
- 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-38-112
- Aircraft type
- Piper PA-38
- 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
- N2539K
- Operator
- Velazquez Ramon L
- Onboard fatalities
- Unknown
- Route
- From Patillas Airport (X64), Patillas, PRTo JRV · Ceiba, PR
- 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
- Takeoff
- 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
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he conducted a preflight inspection before taking off from the paved, 2,000-foot runway. The takeoff was "normal," but the airplane's climb rate was "not enough to clear trees" at the end of the runway. According to a Federal Aviation Administration inspector, the airplane lifted off about 1,500 feet down the runway. The airplane's right wing subsequently hit a tree located to the right of the runway and sustained substantial damage. The inspector also reported no mechanical anomalies and confirmed compression on all engine cylinders. Photographs of the tree indicated that it was about 50 feet beyond and 50 feet to the right of the runway. Straight out and to the left of runway provided a relatively clear pathway. Using the ambient weather conditions, including a 6-knot headwind, the only takeoff performance data available in the pilot's operating handbook indicated that the airplane's takeoff distance to clear a 50-foot obstacle should have been approximately 1,450 feet.
Probable cause
The pilot's inadequate visual lookout and failure to maintain clearance from a tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA090
- Event ID
- 20091203X84042
- Case number
- ERA10CA090
- 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: a83692e4ea734286b748b4198f6b0a8d282d97fde8c85a9cf26d88f8e7075c74; retrieved 2026-09-15T13:32:53.844Z.