Fleet FLEET 16B accident near Bayport, New York, August 18, 2012
On August 18, 2012 at about 9:00 pm local time, a Fleet FLEET 16B, registered N343SF, was substantially damaged in an accident during landing near Bayport, New York (Bayport Aerodrome airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s improper landing flare, which resulted in a hard landing.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 18, 2012 · about 9:00 pm local time · cases in 2012
- Place
- Bayport, New York · Bayport Aerodrome · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Fleet FLEET 16B · all FLEET 16Bs on the register
- Registration
- N343SF · registry record · serial 343
- 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 he returned to the departure airport after a brief local flight and entered the traffic pattern. While on final approach to the runway, he initiated a slip to the left to descend and increase his visibility of the runway. The pilot stated that during previous flights in the tailwheel-equipped biplane, after he exited the slip just before touchdown, the airplane would "float" down the runway in ground effect. However, when he exited the slip during the accident flight, the rate of descent remained constant, and the airplane's contact with the runway was "fairly severe." The landing gear subsequently collapsed, and the airplane departed the right side of the runway and nosed over, resulting in substantial damage to the right upper wing. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation, and that the accident could have been prevented by a "quicker reaction" and "increasing [engine] power to arrest descent rate."
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
- Hard landing during landing defining event
- Landing gear collapse during landing (landing roll)
- Runway excursion during landing (landing roll)
- Nose over/nose down during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained
- cause Personnel issues › Action/decision › Action › (general) › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 1,460 hours in all; 377 in this make and model; 11 in the last 90 days; 4 in the last 30 days; 1,393 as pilot in command
- Last flight review: June 10, 2012
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: rear
- Injury: no injuries
The aircraft
- Airframe total time: 1,635 hours
- Last inspection: annual inspection, August 4, 2012; 1 hours since
- Maximum gross weight: 1,878 lb
- Seats: 2
- Landing gear: fixed
- Engine: Kinner R5 SERIES (piston); 0 hours total
The flight
- Departed from: 23N Bayport NY at 9:00 pm
- Destination: 23N Bayport NY
- Flight plan: none
- Runway 36, 2,740 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 340° at 5 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 3,700 ft
- Temperature: 79°F (26°C), dew point 61°F (16°C)
- Altimeter: 29.82 inHg
- Observation at 8:56 pm from ISP, 3 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
6 documents, released by the NTSB on December 27, 2012. 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, 9 pages | View Download |
| 2 | Memorandum for Record - Pilot | PDF, 1 page | View Download |
| 3 | Memorandum for Record - FAA | PDF, 1 page | View Download |
| 4 | Memorandum for Record - Weather | PDF, 1 page | View Download |
| 5 | Photo 1: Photo of Damage to Right Wing - Courtesy of FAA | PDF, 1 page | View Download |
| 6 | Photo 2: Photo of Damage to Landing Gear Leg Bracing - Courtesy of FAA | 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.
Connections how this case links to the rest of the register
- N343SF on the register today · the tail number may have moved to another aircraft since
- Fleet FLEET 16 26 registered today · the model family and its accident history
- Fleet 92 aircraft on the register
- Engine: Kinner R5 SERIES 157 aircraft carry this series today · as the NTSB recorded it
- Bayport Aerodrome · nearest airport
- Accidents and incidents in New York 1,964 since 1982 · 248 in the last ten years
- New York 6,661 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA12CA520.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.