Cherokee Express Piper PA-60 accident
Piper PA-60 and Cessna 172M · Accident: on ground/water collision with object while taxiing
Event
- NTSB case
- MIA94LA023
- 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
- Charter & commuter
- 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
Aircraft 1 · Piper PA-60
- Aircraft type
- Piper PA-60
- 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
- N91WW
- Operator
- Cherokee Express
- Onboard fatalities
- Unknown
- Route
- From Orlando Executive Airport (ORL)To Tallahassee International Airport (TLH), Tallahassee, FL
- 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 135: Air Taxi & Commuter
- 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
- Taxi
- 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
- On ground/water collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Cessna 172M
- Aircraft type
- Cessna 172
- 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
- N1753V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orlando Executive Airport (ORL)To Orlando Executive Airport (ORL)
- 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
- On ground/water collision with object
- 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 › Clearance, not maintained
- Pilot in command › Visual lookout, not maintained
- Pilot of other aircraft › Clearance, not maintained
- Pilot of other aircraft › Visual lookout, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE TAXIING TO THE ENGINE RUNUP AREA ADJACENT TO RUNWAY 07, THE PILOT OBSERVED TWO OTHER AIRPLANES PARKED ONE BEHIND THE OTHER IN THE RUNUP AREA. THE PILOT STATED GROUND FOG WAS PRESENT AND THE SUN WAS DIRECTLY IN HIS EYES. AS HE TAXIED INTO THE RUNUP AREA, HE COLLIDED WITH THE SECOND AIRPLANE. THE PILOT OF THE OTHER AIRPLANE STATED THE PILOT OF N91WW WAS OBSERVED LOOKING DOWN INSIDE HIS AIRPLANE WHEN THE COLLISION OCCURRED. OFFICIAL SUNRISE WAS 06:52 AND THERE WAS LIGHT FOG IN THE AREA.
Probable cause
THE PILOT-IN-COMMAND'S FAILURE TO MAINTAIN VISUAL LOOKOUT AND CLEARANCE BETWEEN AIRCRAFT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA94LA023
- Event ID
- 20001211X13782
- Case number
- MIA94LA023
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: f2bc8ef435a4f4eb7ace49b3b556bfcbebe86fe50148bc160e2a7fcaa4b904cd; retrieved 2026-09-18T18:25:59.101Z.
- The NTSB's operator name is blank for N91WW; the operator shown is the name the NTSB records it doing business as.