MIA99LA255 · Piper PA-24-250
Piper PA-24-250 · Accident: loss of control on ground/water during landing
From Cross City Airport (CTY) to Albert Whitted Airport (SPG)
Event
- NTSB case
- MIA99LA255
- 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
- N8051P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cross City Airport (CTY), Cross City, FLTo Albert Whitted Airport (SPG)
- 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
- Loss of control on ground/water
- 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 › Brakes(emergency), improper use of
- Pilot in command › Directional control, not maintained
Approximate · Estimated position: the centre of St. Petersburg, FL, the place the record names. Not the accident site.
NTSB narrative
The pilot stated that after a normal landing the airplane initially tracked the runway centerline, but at about 500 feet it veered to the right. The pilot stated that he applied the handbrake which made the situation worse, and the airplane exited the runway. A mechanic who examined the airplane said that the damage was not consistent with a hard landing, but with a sudden stop. The mechanic said that the airplane's hand brake cable is connected to the toe brake cable, and that when the hand brake is applied, it locks the rudder pedals, preventing the pilot from applying rudder input to control the airplane. The mechanic said the rudder trim was 1/3 of the way to the right of center, resulting in the rudder pedals being uneven when the handbrake was applied. The mechanic said that the pilot told him that the landing was normal, and during the rollout he retracted the flaps, turned off the boost pump, and then applied the hand brake, when as a result of applying the hand brake, the airplane veered off the runway. The nose gear right drag link was sent to the NTSB's Materials Laboratory for analysis, and the report shows that the drag link fracture surfaces exhibited a rough, matte gray appearance, consistent with overstress, and the drag link bolt was bent 13 degrees relative to its axis, also consistent with overstress.
Probable cause
the pilots improper use of the hand brake during the landing roll out and his failure to maintain directional control, which resulted in the airplane exiting the runway and incurring substantial damage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99LA255
- Event ID
- 20001212X19831
- Case number
- MIA99LA255
- 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: 1f0854fb1efa9a5b31973718e9ca00d945b1cfc41162ff32131712d9111d0d19; retrieved 2026-09-21T20:23:40.841Z.