BFO93LA186 · Piper PA-24-260
L & L Aviation Piper PA-24-260 · Accident: propeller/rotor contact to person while standing
From an unrecorded airport to W54 · Westminster, MD
Event
- NTSB case
- BFO93LA186
- 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
- 1
- 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-260
- 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
- N8992P
- Operator
- L & L Aviation
- Onboard fatalities
- Unknown
- Route
- From not recordedTo W54 · Westminster, MD
- 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
- Standing · engine(s) operating
- 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
- Propeller/rotor contact to person
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Other person › Clearance, not maintained
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Procedures/directives, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT HE HAD COMPLETED HIS PREFLIGHT INSPECTION, AND RETURNED TO THE OFFICE TO PAY HIS TIE-DOWN FEES FOR THE THREE DAYS. ON HIS RETURN, HE STATED THAT HE STARTED THE ENGINE, CONTACTED GROUND CONTROL FOR TAXI INSTRUCTIONS, BUT WAS UNABLE TO TAXI AS THE NOSEWHEEL CHOCK WAS STILL IN PLACE. HIS WIFE, A NON-PILOT, VOLUNTEERED TO REMOVE THE CHOCK. HE STATED THAT SHE EXITED THE AIRPLANE TO THE RIGHT AND WALKED IN FRONT OF THE RIGHT WING WHERE SHE TRIED TO REMOVE THE CHOCK FROM THE RIGHT SIDE OF THE NOSE GEAR AFT OF THE PROPELLER. SHE WAS STRUCK BY THE PROPELLER. THE PILOT STATED THAT HE HEARD AND FELT A SLIGHT THUD IN THE VICINITY OF THE PROPELLER, SO HE SHUT THE ENGINE DOWN AND EXITED THE AIRPLANE.
Probable cause
THE PILOT'S FAILURE TO FOLLOW STARTING PROCEDURES AND HIS INADEQUATE PREFLIGHT INSPECTION BY NOT REMOVING THE WHEEL CHOCKS AND THE PASSENGER NOT MAINTAINING CLEARANCE FROM THE PROPELLER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA186
- Event ID
- 20001211X13356
- Case number
- BFO93LA186
- 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, damage. 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: 1bde77d2835403275ba14f14327bd65397b8fc176ab54f7ea7009da44886586e; retrieved 2026-09-21T00:22:31.407Z.