NYC93FA015 · Piper PA-28-180
Piper PA-28-180 · Accident: in flight collision with object during landing
From Charlottesville Albemarle Airport (CHO) to Charlottesville Albemarle Airport (CHO)
Event
- NTSB case
- NYC93FA015
- 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
- 1 · 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
Piper PA-28-180
- 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
- N5152L
- Operator
- Jeffrey Brayant
- Onboard fatalities
- Unknown
- Route
- From Charlottesville Albemarle Airport (CHO), Charlottesville, VATo Charlottesville Albemarle Airport (CHO)
- 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
- Landing · aborted
- 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
- In flight collision with object
- 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); Utility pole
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aborted landing, delayed
- Pilot in command › Clearance, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WITNESSES SAW THE AIRPLANE MAKE ONE TOUCH AND GO LANDING AND THEN WATCHED IT AS IT CAME AROUND FOR A SECOND LANDING. ON THE SECOND LANDING, THE AIRPLANE TOUCHED DOWN ON THE APPROACH END OF THE 1800 FEET TURF RUNWAY, AND CONTINUED TO ROLL OUT WITHOUT APPARENT BRAKE APPLICATION. WITH APPROXIMATELY 200 FEET OF RUNWAY REMAINING, THE PILOT ADDED POWER TO THE ENGINE AND THE AIRPLANE BECAME AIRBORNE, BUT IT DID NOT HAVE ENOUGH ALTITUDE TO CLEAR A TREE AND A UTILITY POLE AT THE END OF THE RUNWAY. THE AIRPLANE STRUCK THE TREE, THEN THE UTILITY POLE, AND BURST INTO FLAMES BEFORE HITTING THE GROUND AND COMING TO REST.
Probable cause
THE PILOT'S DELAY IN ABORTING THE LANDING WHICH RESULTED IN INSUFFICIENT RUNWAY REMAINING TO ALLOW THE AIRPLANE TO REACH SUFFICIENT ALTITUDE TO CLEAR THE OBSTACLES AT THE END OF THE RUNWAY
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC93FA015
- Event ID
- 20001211X15927
- Case number
- NYC93FA015
- 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: 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: f3c71af44cdae0d42492924b5582593dc84f7170348fefc4fea081267ffb3015; retrieved 2026-09-21T00:51:46.466Z.