Maule M-7-260C accident near Tampa, Florida, April 23, 2026
On April 23, 2026 at about 7:30 pm local time, a 2019 Maule M-7-260C, registered N41S, was substantially damaged in an accident during landing (aborted after touchdown) near Tampa, Florida (Peter O Knight airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to maintain directional control of the airplane during the aborted landing, which resulted in a runway excursion, collision with a runway sign, and nose over.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 23, 2026 · about 7:30 pm local time · cases in 2026
- Place
- Tampa, Florida · Peter O Knight · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Maule M-7-260C, built 2019 · all M-7-260Cs on the register
- Registration
- N41S · registry record · serial 30061C
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that during landing he flared higher than normal and the airplane bounced on touchdown. While attempting to abort the landing, the pilot applied full power and the airplane subsequently veered left. He attempted to maintain directional control with the rudder pedals, but the airplane continued to the left, exited the runway, hit a runway sign and nosed over. The accident resulted in substantial damage to both wings, fuselage and empennage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control on ground during landing (aborted after touchdown) defining event
- Runway excursion during landing (aborted after touchdown)
- Nose over/nose down during landing (aborted after touchdown)
The NTSB's findings
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 578 hours in all; 255 in this make and model; 22 in the last 90 days; 8 in the last 30 days; 317 as pilot in command
- Last flight review: January 29, 2026
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
Passenger
- Seat: rgt
- Injury: minor injuries
The aircraft
- Airframe total time: 335 hours
- Last inspection: annual inspection, February 20, 2026; 37 hours since
- Maximum gross weight: 2,812 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-540-V4A5D (piston); 337 hours total
The flight
- Flight plan: none
- Runway 22, 3,583 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 220° at 7 knots
- Visibility: 10 statute miles
- Sky: scat at 8,000 ft
- Temperature: 82°F (28°C), dew point 54°F (12°C)
- Altimeter: 29.99 inHg
- Observation at 3:35 pm from TPF
Weather report (METAR): METAR KTPF 231935Z AUTO 22007KT 10SM SCT080 28/12 A2999 RMK AO2 T02820120
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Passengers | 1 |
Photographs from the investigation 2 pictures from the NTSB's docket, as the NTSB released them
The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on June 25, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | Investigative Photographs | PDF, 3 pages · our copy | View Download |
| 3 | Memorandum for Record A�� Event Date Correction | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N41S the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N41S on the register today · the tail number may have moved to another aircraft since
- Maule M-7 275 registered today · the model family and its accident history
- Maule 1,346 aircraft on the register
- Engine: Lycoming IO-540-V4A5D 39 aircraft carry this series today · as the NTSB recorded it
- Peter O Knight Airport · nearest airport
- Accidents and incidents in Florida 6,111 since 1982 · 982 in the last ten years
- Florida 21,728 aircraft registered
- Other NTSB records under N41S 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/ERA26LA184.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

