MIA98LA119 · Piper PA-28-181
Piper PA-28-181 · Accident: propeller/rotor contact to person while standing
From an unrecorded airport to IGY · Chapel Hill, NC
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
- MIA98LA119
- 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-181
- 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
- N4594F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo IGY · Chapel Hill, NC
- 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) start-up
- 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
- Substantial
Cause areas
- Pilot in command › Parking brakes, not set
- Pilot in command › Starting procedure, not followed
Approximate · Estimated position: the centre of Charlotte, NC, the place the record names. Not the accident site.
NTSB narrative
After a preflight, pilot 'A' got into the left seat and pilot 'B' into the right seat and attempted to start the engine, but could not sustain a start. Both pilots exited the airplane and agreed to remove the cowling to determine the problem. Both pilots determined it was not a mechanical problem and pilot 'B' volunteered to get into the airplane and attempt to start the engine. According to pilot 'B''s statement, he told pilot 'A' to 'stay clear of the prop.' He sat in the pilot's seat, looked out and saw pilot 'A' standing to the right of the aircraft, clear of the prop. Pilot 'B' said he 'shouted clear' from the open window on the pilot's side, turned the ignition and the engine 'fired immediately.' He then looked to the right after the engine engaged, saw blood on the wing, and the plane began to race. He said, '...I applied maximum pressure on the toe brakes, but could not stop the plane from moving forward into an open hangar directly in front of the plane. The prop hit a car parked in the hangar and I noticed the right wing bend...fuel start to leak from the tank...the throttle was advanced. I closed the throttle and mixture and the engine finally choked out.' Pilot 'B' then went to the other pilot, rendered aid and called for medical help.
Probable cause
the pilot's failure to follow proper starting procedures.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA98LA119
- Event ID
- 20001211X09906
- Case number
- MIA98LA119
- 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: 305804aa1ee34d7a592dabaf99757d33592e68a35912b2b9e9dfed09aff85e92; retrieved 2026-09-21T11:35:11.577Z.