NYC90LA153 · Piper PA-28
Piper PA-28 · Accident: loss of control on ground/water during landing
From Lee Airport (ANP) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's injuries. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC90LA153
- 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
- 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
- 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
- N3776R
- Operator
- Patrick A. Butcher · private individual
- Onboard fatalities
- Unknown
- Route
- From Lee Airport (ANP), Annapolis, MDTo not recorded
- 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 · flare/touchdown
- 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
- Loss of control on ground/water
- 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
- 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 › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT TOUCHED DOWN AT A REPORTED SPEED OF 80 KNOTS ON A 1900 FOOT HARD, BUMPY RUNWAY. THE PILOT SAID THE AIRCRAFT BECAME UNCONTROLLABLE, AND HE INITIATED A GO-AROUND. DURING THE GO-AROUND, THE AIRCRAFT STRUCK THE WINDSOCK AND CARRIED IT ON THE LEFT WING. THE AIRCRAFT CONTINUED FOR 1/4 MILE, OVER A SLIGHT RISE, AND CAME TO REST IN A ROCK QUARRY. THE AIRCRAFT WAS DESTROYED AND THE THREE OCCUPANTS RECEIVED SERIOUS INJURIES.
Probable cause
A LOSS OF CONTROL UPON TOUCHDOWN AND DURING THE GO AROUND, WHICH RESULTED IN UNCONTROLLED CONTACT WITH THE WINDSOCK AND A ROCK QUARRY. CONTRIBUTING WAS THE EXCESSIVE SPEED OF THE AIRCRAFT (REPORTED 80 KNOTS) UPON INITIAL TOUCHDOWN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC90LA153
- Event ID
- 20001212X23794
- Case number
- NYC90LA153
- 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: d3af71dbf3ba58bfc8e1d861fc6dc73835c1620500f97c8979e382c63c18ac23; retrieved 2026-09-21T15:40:15.786Z.