Amateur-built THOMAS' FLYER accident near Searsmont, Maine, August 13, 2022
On August 13, 2022 at about 6:00 pm local time, a 2007 amateur-built THOMAS' FLYER, registered N35WT, was substantially damaged in an accident during initial climb near Searsmont, Maine (Ridgeview 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
A total loss of engine power during the initial climb for reasons that could not be determined.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 13, 2022 · about 6:00 pm local time · cases in 2022
- Place
- Searsmont, Maine · Ridgeview · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built THOMAS' FLYER, built 2007
- Registration
- N35WT · registry record · serial TF-1
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot, this was the first time that the experimental, amateur-built airplane had been flown in 5 years. An aviation mechanic recently flushed the fuel tanks several times to ensure that they were clean and signed-off a condition inspection. After performing several engine run-ups, the pilot taxied to the active runway and took off. As the airplane climbed between 300 and 500 ft above the ground, the engine sustained a “very brief” stutter, then experienced a complete loss of power. The pilot attempted to return to the airport but was unsuccessful. The airplane descended and impacted on rough terrain near the departure end of the runway. Postaccident examination of the engine did not reveal any preimpact mechanical malfunctions or failures 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 engine power (total) during initial climb defining event
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
The NTSB's findings
- Aircraft › Aircraft power plant › Engine fuel and control › (general) › Unknown/Not determined other cases naming the engine
Pilot
- Certificate: flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; single-engine sea; instructor: airplane single-engine; instrument: airplane; rotorcraft: glider
- Flight time: 3,000 hours in all; 0 in this make and model; 125 in the last 90 days; 50 in the last 30 days; 3,000 as pilot in command
- Last flight review: June 14, 2022
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: frt
- Injury: minor injuries
The aircraft
- Last inspection: condition inspection, August 13, 2022; 40.1 hours since
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-290-D2 (piston); 0 hours total
The flight
- Flight plan: none
- Runway 15, 1,500 ft by 50 ft
Weather at the time
- Light: daylight
- Wind: from 110° at 8 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 7,000 ft
- Temperature: 73°F (23°C), dew point 54°F (12°C)
- Altimeter: 30.05 inHg
- Observation at 2:56 pm from KRKD, 16 miles away
Weather report (METAR): METAR KRKD 131856Z AUTO 11008KT 10SM BKN070 23/12 A3005 RMK AO2 SLP176 T02330122
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them
Photo 1 – Front view of damaged left side cockpit (FAA photo)
Photo 2 – Top view of damaged left wing (FAA Photo)
Photo 3 – View right side of damaged fuselage (FAA Photo)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
4 documents, released by the NTSB on August 21, 2024. 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, 11 pages | View Download |
| 2 | Mfr - FAA Inspector and Mechanic - Wreckage Examination | PDF, 1 page | View Download |
| 3 | NTSB Memorandum - FAA Inspector | PDF, 2 pages | View Download |
| 4 | Investigative Photos | PDF, 3 pages · our copy | 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 N35WT 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
- N35WT on the register today · the tail number may have moved to another aircraft since
- Engine: Lycoming O-290-D2 58 aircraft carry this series today · as the NTSB recorded it
- Ridgeview Airport · nearest airport
- Accidents and incidents in Maine 532 since 1982 · 69 in the last ten years
- Maine 1,427 aircraft registered
- Other NTSB records under N35WT 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/ERA22LA372.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.