NYC90LA112 · Piper PA-24-250
Piper PA-24-250 · Accident: airframe, component or system failure during landing
From D93 · Waterloo, NY to an unrecorded destination
Event
- NTSB case
- NYC90LA112
- 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-24-250
- Aircraft type
- Piper PA-24
- 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
- N7308P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From D93 · Waterloo, NYTo 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 · landing roll
- 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
- Airframe, component or system failure
- 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
- Landing gear, normal brake system › Failure, partial
- Pilot in command › Maintenance, replacement, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE RAN OFF THE END OF THE RUNWAY AND DOWN AN EMBANKMENT AFTER THE LEFT BRAKE FAILED DURING LANDING. THE PILOT SAID HE HAD BRAKES ON THE RIGHT, BUT NOT THE LEFT. THE FAA EXAMINED THE AIRCRAFT AND FOUND THE LEFT BRAKE WORN TO THE POINT THAT THE PISTON EXTENDED BEYOND ITS NORMAL RANGE AND ALLOWED THE SEAL TO LEAK AND THE BRAKE TO FAIL. THEY ALSO SAID THE RIGHT BRAKE HAD FAILED IN A SIMILAR MANNER 4 HOURS PRIOR AND THE OWNER HAD INSTRUCTED THE REPAIR FACILITY TO ONLY REPLACE THE LININGS ON THE RIGHT SIDE.
Probable cause
A WORN OUT BRAKE ON THE LEFT MAIN GEAR. FACTORS RELATED TO THE ACCIDENT WERE: THE OWNER'S DECISION NOT TO REPAIR THE LEFT BRAKE AFTER THE RIGHT BRAKE HAD A SIMILAR FAILURE 4 HOURS EARLIER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC90LA112
- Event ID
- 20001212X23266
- Case number
- NYC90LA112
- 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: 1f7eee1c0a344fe867dd1e73c57f98b963eaa5bf8af10c280ac2d4cd4afb5573; retrieved 2026-09-23T06:10:00.017Z.