Thursday, September 17, 2026

Cessna 441 Conquest II, N128EZ, fatal accident occurred on August 20, 2026, near Cape Newenham Airport (EHM/PAEH), Cape Newenham, Alaska

  • Location: Cape Newenham, AK 
  • Accident Number: WPR26FA309 
  • Date & Time: August 20, 2026, 11:45 Local 
  • Registration: N128EZ 
  • Aircraft: Cessna 441 
  • Injuries: 8 Fatal 
  • Flight Conducted Under: Part 135: Air taxi & commuter - Non-scheduled

https://www.ntsb.gov/investigations/Documents/WPR26FA309%20Prelim.pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N128EZ

On August 20, 2026, at about 1145 Alaska daylight time, a Cessna 441, N128EZ, was destroyed when it was involved in an accident near Cape Newenham, Alaska. The two pilots and six passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 135 on-demand air taxi flight. 

Radio communications between Anchorage Air Route Traffic Control Center (ARTCC) and the flight crew indicated that, following departure from Ted Stevens Anchorage International Airport (ANC), Anchorage, Alaska, the flight crew established communications with the ARTCC while enroute to Cape Newenham LRRS Airport (PAEH), Cape Newenham, Alaska. At the time of departure, the most recent METAR from PAEH reported 10 statute miles (SM) visibility and cloud ceilings at 800 ft above ground level (agl). At about 1016, the flight crew received weather information for PAEH and requested the RNAV Runway 15 approach. The ARTCC subsequently cleared the flight crew to descend at their discretion to 6,000 ft mean sea level (msl). 

At 1027, the controller cleared the flight crew to cross the RNAV (GPS) Runway 15 Initial Approach Fix (IAF), RRLND, at or above 5,000 ft msl and cleared the flight for the RNAV Runway 15 approach. The flight crew responded that they did not want to begin the approach at that time and requested holding instructions. The controller subsequently cleared the flight crew to hold at RRLND with an expected further clearance (EFC) time of 1100. At 1043, the flight crew reported entering the hold at RRLND. The controller acknowledged the report and revised the EFC time to 1130, or earlier upon pilot request. At that time, the Automated Weather Observing System (AWOS) at PAEH reported the wind from 280° at 7 knots 1/4-mile visibility, patches of fog, and overcast 300 ft agl.

At 1102, the flight crew requested and was subsequently cleared by the controller for the RNAV Runway 15 approach. At that time the PAEH AWOS reported 3 miles visibility, mist, and a broken ceiling at 300 ft agl. At 1114, the crew reported they were executing a missed approach, advised the controller that they were operating in visual meteorological conditions, and canceled their IFR clearance. At 1124, the flight crew again contacted ARTCC, reported that the weather conditions at PAEH had improved, and requested an IFR clearance for a second RNAV Runway 15 approach. After confirming the crew could maintain terrain and obstruction clearance to 4,500 ft msl, the controller assigned a transponder code, established radar identification, and cleared the flight for the RNAV Runway 15 approach via IVUXE upon reaching 4,500 ft msl. 

Between 1127 and 1135, the flight crew coordinated with the controller regarding routing for a second RNAV Runway 15 approach. After initially requesting direct routing to IVUXE, the flight crew later requested routing via WAGEN. The controller subsequently cleared the flight crew, upon reaching 4,500 ft msl, to proceed direct to WAGEN, then IVUXE, and direct to PAEH. After reporting level at 4,500 ft msl and later established on the WAGEN-to-IVUXE transition, the flight crew was cleared for the RNAV Runway 15 approach and approved to change frequencies. At that time the PAEH AWOS reported 1/4 mile visibility, fog, and an overcast ceiling at 300 ft agl. No further radio communications were received from the flight crew. 

According to preliminary ADS-B data, the airplane departed from runway 7L at ANC at 0911:54. After departure the airplane climbed to an altitude of about 625 ft msl and initiated a climbing right turn to a southwest heading. 

At 0924:29, the airplane climbed through an altitude of about 16,175 ft msl and entered a right turn to a westerly heading. The data showed the airplane continued climbing to flight level 280 while proceeding west toward PAEH. When the airplane was about 123 miles northeast of the Initial Approach Fix (IAF) RRLND, it began a descent. The airplane crossed RRLND at about 10,375 ft msl and subsequently performed a series of descending turns in the vicinity of the GPS fix, consistent with holding. 

At 1104:31, while at an altitude of about 4,400 ft msl, the airplane turned westbound toward the Intermediate Fix (IF) IVUXE. At 1107:31, the airplane approached IVUXE at about 2,100 ft msl and initiated a left turn toward the Final Approach Fix (FAF) KRSSS. The last recorded altitude north of KRSSS was about 1,025 ft msl prior to ADS-B contact being lost at 1110:13. When ADS-B resumed at 1111:16, the airplane continued on the final approach, until contact was lost at 1111:40, the airplane was about 2.3 miles north of the Missed Approach Point (MAP) CFKMW at an altitude of about 425 ft msl. (See figure 1.)

ADS-B contact was reestablished at 1114:21 while the airplane was on a northerly heading at about 1,300 ft msl. It continued northbound past IVUXE and approached FELTI (located about 21 miles north of IVUXE) at about 2,100 ft msl. The airplane then completed a 180° left turn to a southerly heading toward IVUXE. At 1130:04, the airplane had climbed to an altitude of 3,925 ft msl and had initiated a right turn to the west, as it approached the WAGEN IAF. Between 1132:40 and 1135:56, there were several periods where ADS-B contact was lost. When ADS-B contact resumed at 1135:56, the airplane was at 4,425 ft msl on an easterly heading toward IVUXE. 

At 1138:15, the airplane was at an altitude of about 2,850 ft msl when it initiated a right turn near IVUXE. At 1141:14, the airplane crossed KRSSS at about 2,400 ft msl and continued southbound along the approach course. At 1143:18, the airplane crossed the MAP CFKMW at about 1,000 ft msl. The airplane continued beyond CFKMW, while it descended to about 600 ft msl, until ADS-B contact was lost at 1143:51. At that time, the airplane was about 1.3 miles north of the runway 15 threshold at PAEH. (See figure 2.)

A review of the RNAV (GPS) RWY 15 instrument approach plate, PAEH, dated 09 July 2026, showed Lateral Navigation (LNAV) Minimum Descent Altitude (MDA) as 1320 ft and 3 miles visibility. The MAP was located 2.2 miles north of the runway 15 threshold. Two cautions were noted: “1) Rwy located on slope of 2306’ mountain. High terrain both sides and S end of rwy.” and “2) Successful go-around improbable if initiated past the MAP.”

Technicians who were stationed at the facility near PAEH provided statements to investigators. One technician stated that he performed a routine inspection of the runway at about 0900 on the morning of the accident. As part of this inspection, he drove the length of the runway to check the condition of the runway surface and to ensure there was no wildlife within 100 yards of the runway. At that time, he did not observe any anomalies or foreign objects on the runway and did not see any wildlife. The technician noted that he typically performs another runway inspection to ensure the runway is clear before an airplane is expected to land; however, he was unable to complete a runway inspection for the accident airplane’s arrival because of thick fog that blanketed the runway. 

According to the second technician, the facility featured a dedicated weather building located about 0.3 miles west of the approach end of runway 15. The building housed an aviation radio and terminal that displayed weather information from the AWOS equipment, which was located near the runway. In addition, charts and photographs in the weather building provided the distances and elevations of nearby landmarks. 

At about 0800 or 0830 on the morning of the accident, the technician placed a phone call to the operator to provide the weather conditions at PAEH. In the hours following this call, the technician observed that the cloud ceilings and visibility had decreased. 

Before the airplane began its first approach to PAEH, the technician went to the weather building. The technician used the radio to relay the conditions indicated by the AWOS, augmented by his observation of the visibility reference points listed on the weather building charts. He noted that when the airplane performed its first approach, a reference point that was 1 7/8 miles away from the weather building was obscured by fog. After the airplane performed the missed approach, the flight crew told the technician that they were going to attempt to land at Platinum Airport (PAPM), Platinum, Alaska, about 23 miles north of PAEH. The technician stated that, after the airplane’s first approach, he initially could see small areas of blue sky to the north, but the visibility at PAEH had diminished further. 

Several minutes later, the flight crew reestablished radio contact with the technician, stating that they had been unable to contact PAPM on the radio and wanted to perform a second approach to PAEH. The technician stated that, by the time the airplane had begun its second approach, none of visibility reference points were visible, and he could no longer see the runway. When the flight crew reported they were two minutes out, the technician relayed the AWOS weather reading and noted to himself that he did not have any visual references from the weather building. 

Shortly thereafter, the technician heard “normal motor sounds” as the airplane approached the runway. He then heard the engines “throttle up,” followed by a “backfire,” after which the sounds ceased. After unsuccessful attempts to locate the airplane on ground or to contact the flight crew by radio, the technician and other personnel from the facility began to search for the airplane. The wreckage was located in an area of rising terrain about 0.5 miles west of the approach end of runway 15. 

Examination of the accident site revealed the first identifiable point of contact (FIPC) was an area of disturbed rocks measuring about 6 ft by 6 ft, which exhibited evidence of fire, at an elevation of about 610 ft mean sea level (msl). The debris path extended approximately 160 ft on a true heading of about 250° and continued upslope onto a small, relatively level rocky area. The main wreckage came to rest on its left side on a true heading of approximately 120°, about 160 ft from the FIPC. Wreckage distributed along the debris path included fragments of the wings, fuselage, propeller blades, flaps, and ailerons. All major structural components of the airplane were identified at the accident site. 

The wreckage is pending recovery to a secure location for further examination.  

Mooney M20F Executive 21, N9546M, fatal accident occurred on September 7, 2026, near Space Coast Regional Airport (TIX/KTIX), Titusville, Florida

  • Location: Titusville, FL 
  • Accident Number: CEN26FA310 
  • Date & Time: September 7, 2026, 10:15 Local
  • Registration: N9546M
  • Aircraft: Mooney M20F 
  • Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203748/pdf\

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N9546M

On September 7, 2025, about 1015 eastern daylight time, a Mooney M20F airplane, N9546M, was destroyed when it was involved in an accident near Titusville, Florida. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. 

Airplane position data revealed that the flight departed from runway 36 (taxiway Charlie intersection) at the Space Coast Regional Airport (TIX), Titusville, Florida. About 1015:07, the airplane overflew the departure end of the runway. About that time, it entered a left turn and climbed to a maximum altitude of about 220 ft mean sea level (msl). The left turn continued until the final data point was recorded at 1015:27. The altitude associated with the final data point was 220 ft msl, and the airplane was oriented on a southwest heading at that time. 

Surveillance video footage from a camera located at the Executive Jet Center fixed base operator depicted the airplane as it departed. Initially, the airplane became airborne and began to climb. However, soon afterward, it entered a descent. As it neared the end of the runway, the airplane began to climb again and subsequently entered a left turn. The turn continued until the airplane ultimately descended behind an intervening tree line. Shortly afterward, a plume of smoke was visible rising above the trees. 

A witness positioned outside the museum on the east side of the airport reported observing the airplane. Initially, she thought that the pilot was descending to execute a touch-and-go but then the airplane started to climb. She noted “a lot of noise” from the airplane as it climbed; however, that noise stopped shortly afterward as it neared the end of the runway. The airplane then entered a left turn and, ultimately, impacted power lines. 

The airplane struck a set of powerlines before coming to rest inverted on the westbound traffic lanes of Route 405/Columbia Blvd immediately north of the airport property. A post-impact fire ensued. The accident site was about 0.29 miles northwest from the departure end of runway 36.

The cockpit area, including the instrumentation and avionics, was consumed. The outboard section to the left wing was separated and located near the main wreckage consistent with the powerline impact. The aft fuselage was deformed and buckled that was consistent with impact forces. The empennage remained attached with exception of the upper 2-ft section of the rudder which was separated and located in the debris path. The nose landing gear and left main landing gear were in the extended position. The right main landing gear was separated and located in the debris path.

Diamond DA20-A1 Katana, N83RF, fatal accident occurred on August 20, 2026, near Bristol, Maine

  • Location: Bristol, ME 
  • Accident Number: ERA26FA310 
  • Date & Time: August 20, 2026, 12:59 Local 
  • Registration: N83RF 
  • Aircraft: DIAMOND AIRCRAFT IND INC DA20-A1 
  • Injuries: 1 Fatal, 1 Minor 
  • Flight Conducted Under: Part 91: General aviation - Personal 

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203632/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N83RF

On August 20, 2026, about 1300 eastern daylight time, a Diamond Aircraft Ind Inc DA20-A1, N83RF, was substantially damaged when it was involved in an accident near Bristol, Maine. The pilot was fatally injured, and the pilot-rated passenger sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. 

The pilot-rated passenger reported that the flight originated from Brunswick Executive Airport (BXM), Brunswick, Maine, with intentions of overflying points of interest before landing at its intended destination of the Knox County Regional Airport (RKD), Rockland, Maine. About 20 minutes after departure, they observed a low engine oil pressure indication and the pilot elected to divert to RKD. Shortly thereafter, they experienced several “buffets” from the engine along with an odor of smoke in the cockpit, which was followed by a total loss of engine power. The pilot initiated a right turn and performed a forced landing on a state park road about 24 miles southwest of RKD. During the landing, the airplane traversed a grassy area, impacted trees and shoreline rocks, and then came to rest inverted in about 4 ft deep water along the Pemaquid Harbor shoreline. 

The identified touchdown point was three linear tire impressions in the grass about 50 ft in length, consistent with main and nose landing gear, about 40 ft from the road on a 220° magnetic course, and about 540 ft from the main wreckage. The airplane impacted a sign about 65 inches above ground level and 80 ft from the tire impressions. A green wingtip navigation light was observed at the base of the sign. The airplane then struck a raised wooden structure surrounding a horseshoe pit and two trees that were located about 40 ft apart near the shoreline (see figure 1). All major components of the airplane were located at the accident site. 

The airplane was recovered to a secure facility, and a postaccident examination was conducted. The left wing exhibited impact damage to its outboard leading-edge and aft wing root. The right wing was separated from the fuselage with impact damage noted to its outboard leading-edge. The flaps were observed fully extended, consistent with a landing configuration. Impact damage was noted to the top of the horizontal stabilizer. Rudder and elevator control continuity was established from the flight controls in the cockpit to the respective flight control surfaces in the empennage. Aileron control continuity was established from the flight controls in the cockpit to the left aileron and the right aileron impact separated control tube. The engine cowlings and canopy were fragmented. The pilot and copilot 4-point restraints remained attached and could be latched and unlatched without any anomalies. Both engine propeller blades were fractured with no rotational abrasions or leading-edge damage. 

The engine’s reduction gear box was fractured from impact forces. The crankshaft could not be rotated by hand. Examination of the engine revealed the No. 4 cylinder exhaust valve face was separated from the stem, and a hole was observed in the piston dome with impact damage noted to the interior of the cylinder and head. Residual oil was noted in the interior of the crankcase and about 2 quarts of oil was present in the reservoir. The oil pump rotated freely when actuated by hand. There was no evidence of an in-flight or postaccident fire. 

The wreckage was retained for further examination.

Lancair Evolution, N305PV, fatal accident occurred on September 3, 2026, near Tampa Executive Airport (VDF/KVDF), Tampa, Florida

  • Location: Tampa, FL 
  • Accident Number: ERA26FA326 
  • Date & Time: September 3, 2026, 08:15 Local 
  • Registration: N305PV 
  • Aircraft: MACLURA LLC EVOLUTION 
  • Injuries: 2 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203727/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N305PV

On September 3, 2026, about 0815 eastern daylight time, an experimental, amateur-built Evolution airplane, N305PV, was destroyed when it was involved in an accident near Tampa, Florida. The commercial pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. 

According to preliminary information obtained from the FAA, an instrument flight rules (IFR) flight plan was filed for the accident flight departing from Tampa Executive Airport (VDF), Tampa, Florida, with a destination of Elizabeth City Regional Airport (ECG), Elizabeth City, North Carolina. Review of air traffic control data revealed that the pilot acknowledged and correctly read back his IFR clearance and takeoff instructions. The instructions were to fly runway heading (050°) to 2,000 ft and expect 17,000 ft, 10 minutes after departure. No further communications were received from the accident airplane. 

Review of ADS-B data and security video revealed that the airplane lifted off and turned left, approximately halfway down the 5,000-ft-long runway, at a groundspeed about 80 knots. The airplane flew a 180° left turn in a nose-high, steep left bank, before it descended nose-down into terrain. 

The wreckage was located in a wooded area of a state water management facility, about 1/3- mile northwest of the touchdown zone for runway 5 at VDF. A debris path was observed, originating with severed tree branches, followed by ground scars, and then terminating at the main wreckage. The debris path was approximately 70 ft-long, on a magnetic course of 220°, and at a descent angle about 35° through the trees. The wreckage came to rest inverted, on a magnetic heading of 310°, and a majority of the airplane’s composite airframe was consumed by a postcrash fire. 

All major components of the airplane were identified. The engine remained attached to the firewall at the front of the wreckage. Three of the five composite propeller blades remained attached to the hub. The inboard sections of both wings were located behind the engine. The empennage was consumed by fire with the exception of a rudder counterweight and pieces of the rudder that were located underneath the main wreckage.

The pilot held a commercial pilot certificate with ratings for airplane single engine land, airplane single engine sea, and instrument airplane. He was operating under the provisions of BasicMed with his most recent examination and course completed on April 25, 2026. Review of training records revealed that he reported 1,203 total hours of flight experience when he began initial transition training for the make and model airplane on August 26, 2025. 

The airplane was assembled from a kit in 2020 and issued an FAA experimental airworthiness certificate. It was powered by a Pratt and Whitney PT6A-135A, 550-horsepower turboprop engine, driving a five-blade constant speed Hartzell propeller. The airplane’s most recent condition inspection was completed on August 26, 2026. At that time, the airframe and engine had accumulated 581 hours since new.

The wreckage was retained for further examination.

Piper PA-24-260 Comanche, N9485P, fatal accident occurred on August 26, 2026, near Seldovia Airport (SOV/PASO), Seldovia, Alaska

  • Location: Seldovia, AK 
  • Accident Number: ANC26FA091 
  • Date & Time: August 26, 2026, 13:17 Local 
  • Registration: N9485P 
  • Aircraft: Piper PA-24-260 
  • Injuries: 4 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203672/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N9485P

On August 26, 2026 about 1317 Alaska daylight time, a Piper PA-24-260 airplane, N9485P, was substantially damaged when it was involved in an accident near Seldovia, Alaska. The pilot and three passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. 

The pilot and three passengers departed from Merrill Field Airport (PAMR), Anchorage, Alaska, for a day flight to Seldovia Airport (PASO), Seldovia, Alaska. A witness at the Seldovia airport heard the airplane approaching to land on runway 16 and the airplane appeared to be coming in fast. He then heard a series of bounces which sounded hard and abnormal. The first bounce was loud and not a normal touchdown sound. He heard a second bounce which also sounded hard and abnormal. He visually saw the third bounce and believed that the nosewheel hit the ground first. He then heard the engine go to full throttle. He stated that the aircraft pitched up very high and possibly had a tail strike. A witness working with heavy equipment near the end of the runway saw the airplane and noted the airplane was unusually low to the ground just past the end of the runway. He further noted that the accident airplane had attempted to land in the opposite direction of other airplanes that had been landing. Multiple ground witnesses reported seeing the airplane unusually low to the ground, the engine being very loud, and the airplane impacting a tree before descending into the water. 

The FAA’s chart supplement for the airport notes that surface of the Seldovia Airport runway is gravel and the length is 1,845 ft. The slope to clear obstructions for runway 16 is 11:1. The supplement notes 158 ft trees, 1,735 ft from runway 16 and 110 ft left of the centerline. For runway 34, the supplement notes an 89 ft tree, 995 ft from the runway, and 140 ft right of the centerline. 

The Automated Surface Observing System (ASOS) weather station at the airport at the time of the accident was reporting wind from 020 at 5 knots with wind gusts at 9 knots.

The airplane came to rest about 2,200 ft from the end of runway 16 into the Seldovia Slough. A detailed wreckage examination is pending.  

Bell OH-58A Kiowa, N480FT, accident occurred on September 3, 2026, near Phoenix, Arizona

  • Location: Phoenix, AZ 
  • Accident Number: WPR26LA328 
  • Date & Time: September 3, 2026, 09:32 Local 
  • Registration: N480FT 
  • Aircraft: Bell OH-58A 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Instructional 

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203732/pdf

https://registry.faa.gov/aircraftinquiry/Search/NNumberResult?NNumberTxt=N480FT

On September 3, 2026, about 0932 mountain standard time, a Bell OH-58, N480FT, sustained substantial damage when it was involved in an accident near Deer Valley, Arizona. The pilots did not sustain any injuries. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. 

The helicopter instructor reported he and a pilot-rated student departed from Phoenix Deer Valley Airport, Phoenix, Arizona to practice approaches, hovering autorotations, and autorotations with a power recovery in the local area. After completing the approaches and a hovering autorotation without incident, the instructor landed the helicopter and briefed the student about the autorotation with a power recovery procedure. 

Shortly after, the instructor and the student both demonstrated a successful autorotation with a power recovery. With the instructor on the controls and the helicopter about 500 ft above the ground (agl) and 70 knots indicating, the instructor initiated the third autorotation. The instructor noted that the entry was smooth and announced the main rotor rpm settled around 100% and that the N1 needle was around 62%, at idle engine power. About 200 ft agl and 60 knots, the instructor rolled the throttle to full power and joined the rotor rpm needle with the engine's rpm needle. 

As the helicopter crossed about 50 ft agl, the instructor initiated a flare and about 10-15 ft agl, he applied slight aft cyclic to slow the descent rate and terminate the recovery to a 3-5 ft agl hover. During the aft pitch control input, the low rotor RPM warning horn became audible and the instructor noted that he did not receive an engine response after he increased the throttle setting. The instructor quickly raised the collective lever to cushion the landing; however, the helicopter continued its descent and impacted terrain. Subsequently, the main rotor system separated from the mast and the helicopter sustained substantial damage to the fuselage, main rotor system, and drive train.

The airplane was recovered to a secure facility for further examination.

Cessna 150E, N3037J, accident occurred on September 1, 2026, near Siler, Washington

 

  • Location: Siler, WA 
  • Accident Number: WPR26LA327 
  • Date & Time: September 1, 2026, 12:20 Local 
  • Registration: N3037J 
  • Aircraft: Cessna 150E 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/203722/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N3037J

On September 1, 2026, at 1220 Pacific daylight time, a Cessna 150E, N3037J, sustained substantial damage when it was involved in an accident near Siler, Washington. The pilot and pilot rated passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. 

The pilot reported that he was conducting a cross-country flight from Jefferson County International Airport (0S9), Port Townsend, Washington to Packwood Airport (55S), Packwood, Washington. The pilot established a cruise altitude of 5,500 ft mean sea level above a cloud layer. Once the airplane was no longer above clouds and was approaching their intended destination, he initiated a descent, reduced engine power, and applied carburetor heat. Subsequently, the pilot noticed a 300 rpm decrease and that the engine was running rough. He advanced the throttle; however, engine rpm did not increase. The pilot attempted to restore engine power by enriching the mixture, cycling the magnetos, and cycling the carburetor heat. Despite his attempts, the pilot was unable to restore engine power and initiated a forced landing to a riverbed since the airplane was unable to maintain altitude. During the landing sequence, the airplane sustained substantial damage to the fuselage. 

The airplane was retained for further examination.