FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW95LA289 · Cessna 182

11 Jul 1995 · Port Sulphur, LA, United States

Cessna 182 · Accident: overrun during landing

From Lakefront Airport (NEW) to an unrecorded destination

Report a problem

Event

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

Cessna 182

Aircraft type
Cessna 182
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
N2878R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lakefront Airport (NEW), New Orleans, LATo not recorded
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 › Ground loop/swerve, intentional
  • Pilot in command › Short field landing/procedure, misjudged

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

NTSB narrative

WHILE CIRCLING OVERHEAD THE 1,500 FOOT PRIVATE GRASS AIRSTRIP, THE PILOT OBSERVED 'STANDING WATER' AND POWER LINES AT THE EAST END OF THE RUNWAY. THE PILOT ELECTED TO LAND FROM THE WEST TO AVOID THE WATER AND THE POWER LINES. THE PILOT REPORTED THAT, DURING THE LANDING ROLL OUT, 'NORMAL BRAKING WAS NOT EFFECTIVE IN SLOWING THE AIRCRAFT DOWN.' IN ORDER TO AVOID CONTACTING AN EMBANKMENT AT THE END OF THE RUNWAY, THE PILOT 'ATTEMPTED TO GROUND LOOP THE AIRCRAFT.' SUBSEQUENTLY, THE LEFT WING AND PROPELLER STRUCK THE GROUND.

Probable cause

THE PILOT'S MISJUDGEMENT OF HIS SHORT FIELD LANDING RESULTING IN AN INTENTIONAL GROUND LOOP TO AVOID AN OVERRUN. FACTORS WERE THE REDUCED BRAKING EFFECTIVENESS ON THE WET GRASS RUNWAY.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW95LA289
Event ID
20001207X03949
Case number
FTW95LA289
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: bcf42221931619ebb1397d86d183d04c0ff5ea889a5db2a4a437f08ab1fc10d6; retrieved 2026-09-22T23:38:47.102Z.