FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA04CA118 · Piper PA-28-151

24 Jul 2004 · Sugar Loaf Key, FL, United States Narrative disagrees

Piper PA-28-151 · Accident: overrun during landing

From Naples Municipal Airport (KAPF) to Sugar Loaf Shores Airport (7FA1)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
MIA04CA118
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
Unknown
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-151

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
N4590F
Operator
Troy Zinser
Onboard fatalities
Unknown
Route
From Naples Municipal Airport (KAPF), Naples, FLTo Sugar Loaf Shores Airport (7FA1), Sugar Loaf Key, 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 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
Overrun
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 › Proper touchdown point, not attained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that after starting the engine at the departure airport he checked the brakes with no discrepancies noted. Additionally, no discrepancies were noted with the brakes during the engine run-up before departure. The flight departed and nearly the entire flight was uneventful with the exception of a momentary discrepancy with the alternator. The flight arrived at the destination airport on the base leg where he lowered 1 notch of flaps. The flight then turned final for runway 10, where he fully extended the flaps and maintained approximately 65. He reported landing within the first 1/3 on the 2,700 foot long runway and applied the normal brakes but later reported he, "...got nothing." He repositioned his feet thinking he might be pushing on the rudder bar instead of the brake pedals but again there was no effect. During the landing roll he contemplated performing a go-around but decided not to due to the length of the runway. The airplane continued off the end of the runway and collided with brush. After coming to rest, he and the passengers evacuated the airplane. After getting out of the airplane, he looked back and saw skid marks in the sand area beyond the departure end of the runway. He also stated that he was familiar with the accident airport as he had flown in there previously approximately 7-8 times. Following recovery of the airplane, examination of the brake system by the insurance adjuster revealed no evidence or malfunction.

Probable cause

The failure of the pilot to attain the proper touchdown point resulting in a landing overrun and subsequent on-ground collision with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA04CA118
Event ID
20040917X01452
Case number
MIA04CA118
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: fd49ead4eb5ea2db27ee3fd94873d86c183c429f31fcc7ed43c5ff5a19c206a1; retrieved 2026-09-22T06:59:05.547Z.