FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14LA159 · Cessna 500

16 Mar 2014 · Zephyrhills, FL, United States

JJ Aeronautics Cessna 500 · Accident: runway excursion during landing

From Miami-Opa Locka Executive Airport (OPF) to Zephyrhills Municipal Airport (ZPH)

Report a problem

Event

NTSB case
ERA14LA159
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

Cessna 500

Aircraft type
Cessna 500
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
N125DS
Onboard fatalities
Unknown
Route
From Miami-Opa Locka Executive Airport (OPF), Opa Locka, FLTo Zephyrhills Municipal Airport (ZPH), Zephyrhills, FL
Aircraft age
About 39 years (built 1975)
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
Defining eventThe 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
Runway excursion
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The two flight crewmembers reported that, after landing on runway 36, the pilot, who was the pilot flying, applied the brakes normally; however, the airplane did not decelerate as expected. The pilot applied the brakes a second time, and the right main landing gear tire subsequently failed. The airplane departed the end of runway 36 and came to rest in an area of unfinished gravel, which resulted in structural damage to the airframe.

Examination of the 4,954-feet-long runway revealed that the airplane touched down about 1,400 feet from the approach end. Skid marks were visible for about 2,982 feet, and the tire failure occurred about 3,153 feet into the landing. Examinations revealed that the right main landing gear tire had a flat spot with a 4-inch diameter hole consistent with a locked brake. The airplane was equipped with an optional antiskid wheel braking system; however, it was disabled in 2004.

The pilots reported that they decided to land on runway 36 based on the wind at flight level 180 and that they did not check the surface wind at the airport. The surface wind at the airport at the time of the accident was from 158 degrees at 15 knots gusting to 25 knots. Thus, the airplane landed with a significant quartering tailwind, which resulted in it touching down at a location and speed at which the pilots were unable to stop the airplane on the runway using normal braking.

Probable cause

The pilots' inadequate in-flight planning and improper selection of runway 36 for landing, which resulted in a significant quartering tailwind during the landing, exceedance of the airplane's braking capability, and a subsequent runway overrun.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14LA159
Event ID
20140320X34640
Case number
ERA14LA159
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 70ee037b2e3702b787ac4f972c50f36fd53e2ebd5eb99a04e1bab8df575c93dc; retrieved 2026-09-15T23:25:12.157Z.