ERA26FA115 · Cessna A185 F
Cessna A185 F · Accident: dragged wing/rotor/float/other during landing
From Marco Island Executive Airport (MKY) to an unrecorded destination
Event
- NTSB case
- ERA26FA115
- 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
- 1 · 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 A185 F
- Aircraft type
- Cessna 185
- 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
- N7574N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Marco Island Executive Airport (MKY), Marco Island, FLTo not recorded
- Aircraft age
- About 45 years (built 1981)
- 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 · flare/touchdown
- 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
- Dragged wing/rotor/float/other
- 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
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 February 15, 2026, about 1155 eastern standard time, a Cessna A185F, N7574N, was substantially damaged when it was involved in an accident near Everglades City, Florida. The pilot was seriously injured, and the passenger was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to preliminary ADS-B data, the airplane departed from Marco Island Executive Airport (MKY), Marco Island, Florida at 1116 and flew southeast toward the coastline. The airplane followed the coastline and performed multiple turns until it reached Pavilion Key, Florida. After flying over Pavilion Key, the airplane turned northwest and proceeded back up the coastline. About 5 miles west of Everglades City, Florida, the airplane made multiple low altitude maneuvers while flying over the Ten Thousand Islands portion of the Everglades National Park. The last ADS-B data point was about .5 mile east of the accident site. The airplane was located in the Ten Thousand Islands portion of the Everglades National Park upside down in the water. At high tide, it was observed that only the floats of the airplane were above the water line, during low tide, the floats and about half of the airplane’s fuselage were above the water line. The airplane was equipped with amphibious landing gear which was found in the “UP” (water landing) position. The water rudders were also found in the “UP” position. During the recovery of the wreckage, the airplane was turned upright, onto its floats, and towed to shore. The floats supported the weight of the airplane for several hours during the tow. After recovery, a postaccident examination of the wreckage revealed the airplane had sustained substantial damage to the fuselage, with the majority of the damage contained to the forward portion of the airplane. Flight control continuity was established from the cockpit to all associated flight controls by manipulating the cockpit controls and observing corresponding surface movement. Binding was noted in the rudder pedals consistent with damage to the right water rudder sustained during recovery. No other flight controls exhibited unusual resistance. The flap handle was impact damaged and found in the 1st detent which is equal to 10° of flaps; however, the flaps operated normally. The horizontal stabilizer trim jack screws were measured to be 5.5 inches and was near the nose up stop. The airplane was equipped with a 3-point shoulder harness seatbelt system for the front seats. The pilot side restraint remained attached to its installation points and was undamaged. The belt buckle was found unlatched and operated normally during testing. The copilot side restraint system remained attached to its attach points, and one of the harness restraints was cut. The belt buckle was found unlatched and operated normally during testing. The pilot seat was equipped with the inertia reel secondary seat stop, which functioned normally during testing. The wreckage was retained for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA26FA115
- Event ID
- 20260215202436
- Case number
- ERA26FA115
- 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. 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: a721d94c54357de769e0db0ad71ccc9d1efbd8d71093bbc862376cebd9847e0f; retrieved 2026-09-15T09:13:38.191Z.