FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25FA144 · Cessna 210L

2 Apr 2025 · Raceland, LA, United States

Southern Seaplane Cessna 210L · Accident: loss of control in flight on approach

From Southern Seaplane Airport (65LA) to an unrecorded destination

Report a problem

Event

NTSB case
CEN25FA144
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
Ongoing
API-reported fatalities
2 · 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
Instrument Meteorological Cond

Cessna 210L

Aircraft type
Cessna 210
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
N1574P
Onboard fatalities
Unknown
Route
From Southern Seaplane Airport (65LA), Belle Chase, LATo not recorded
Aircraft age
About 49 years (built 1976)
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
Approach
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

On April 2, 2025, at 2030 central daylight time, a Cessna 210L airplane, N1574P, was destroyed when it was involved in an accident near Raceland, Louisiana. The pilot and flight instructor were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 instructional flight. Southern Seaplane, Inc., the airplane owner/operator, informed investigators that the accident pilot had recently reached 500 hours of total flight experience, and that the purpose of the accident flight was to provide the pilot the opportunity to gain more night flight experience and to conduct an instrument proficiency check of the pilot by the instructor that was on-board the airplane. The operator indicated that they intended to add the accident pilot to their on-demand air charter certificate sometime in the future and were helping her gain the experience necessary. The operator said the intended route of flight was to originate from the Southern Seaplane Airport (65LA), Belle Chase, Louisiana, fly to the Houme-Terrebonne Airport (HUM), Houma, Louisiana, perform an instrument approach, fly to the South Lafourche Leonard Miller Jr. Airport (GAO), Galliano, Louisiana, perform another instrument approach, and then return to 65LA. Preliminary flight track data indicated that the airplane departed 65LA about 2000 and proceeded toward the west. The flight contacted the New Orleans Approach control facility and requested to fly a practice ILS (instrument landing system) approach into HUM. The flight later requested an instrument flight rules clearance since they would need to penetrate the clouds during the flight. A clearance was issued and the controller provided vectors for the ILS runway 18 approach to HUM. During the flight, the flight crew requested a climb to 3,000 ft msl to attempt to get out of turbulence, which was granted by the controller. The controller continued issuing vectors for the Runway 18 ILS approach to HUM and ultimately cleared the flight for the approach. The flight acknowledged the approach clearance, and the controller authorized a frequency change to the HUM advisory frequency. No further communications were recorded from the accident airplane. The reported weather conditions at HUM about the time of the accident included wind from 140° at 19 knots, gusting to 26 knots, 7 statute miles visibility, overcast ceiling at 1,400 ft. temperature 26° C, dew point 23°C, altimeter setting 29.89 in-Hg. The airplane impacted a marsh about 7.5 nm north of HUM. The only part of the airplane visible above the surface of the marsh was the left wing. The wreckage was confined to a small area and the wreckage signatures were consistent with a near vertical impact. The airplane wreckage was recovered from the marsh and a layout examination performed. Several components of the airplane and engine were not located during recovery from the accident scene; however, examination confirmed the presence of all primary aircraft structures and flight control surfaces. The airplane’s engine and all three propeller blades were also recovered from the accident scene. The airplane’s instrument panel and firewall were not found during the recovery.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record CEN25FA144
Event ID
20250403199955
Case number
CEN25FA144
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2025-04-03.
  • API snapshot SHA-256: 9ce8acb99947a32c7f9920ba839648a7a8f6a52bdcfd2defd02439900ff41e3b; retrieved 2026-09-15T09:03:35.668Z.