Accident Beechcraft A24R Sierra 200 N8020R, Friday 21 October 2022
ASN logo
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Friday 21 October 2022
Time:18:45
Type:Silhouette image of generic BE24 model; specific model in this crash may look slightly different    
Beechcraft A24R Sierra 200
Owner/operator:Monadnock Aviation
Registration: N8020R
MSN: MC-13
Year of manufacture:1970
Total airframe hrs:5083 hours
Fatalities:Fatalities: 2 / Occupants: 2
Other fatalities:0
Aircraft damage: Destroyed
Category:Accident
Location:Keene, NH -   United States of America
Phase: Take off
Nature:Private
Departure airport:Keene-Dillant-Hopkins Airport, NH (EEN/KEEN)
Destination airport:Keene-Dillant-Hopkins Airport, NH (EEN/KEEN)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
On October 21, 2022, about 1845 eastern daylight time, a Beech A24R, N8020R, was destroyed when it was involved in an accident near Keene, New Hampshire. The flight instructor and commercial-rated pilot were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

A mechanic reported that the maximum engine rpm attained during a postmaintenance fullpower engine run earlier on the day of the accident was between 2,300 and 2,375 rpm; he approved the airplane to return to service. (A maximum continuous power setting of 2,650 to 2,700 rpm was required.) The airplane had not flown in about 14 months. A postmaintenance check flight was not performed after the annual inspection.

A flight instructor and a pilot under instruction were initiating a personal flight, which was the airplane’s first flight after the annual inspection was completed. Coincidentally, it was also their first flight in the same airplane in which they experienced poor takeoff and climb performance during a flight nearly 14 months earlier.

Witnesses reported that during the accident takeoff roll, the engine did not sound normal, with one reporting that it never sounded smooth the entire time the airplane was on the runway or while airborne. The airplane became airborne about 3,311 ft down the 6,201-ft runway, which was about 2,087 ft more takeoff distance than the calculated value for the environmental conditions that day. After becoming airborne, the airplane leveled off at 25 ft followed by a momentary power reduction and then a power advance. The flight continued in a shallow climb, climbing no higher than about 50 to 200 ft when the flight was about 5,200 ft down the runway with about 1,000 ft of runway remaining. The flight continued off the airport where the “poor” engine sound continued. While maintaining controlled flight, the airplane impacted a storage structure attached to an apartment building, resulting in a postimpact fire that nearly consumed the airplane.

Postaccident examination of the engine revealed that none of the two-piece fuel injector nozzles had inserts or restrictors installed The mechanic reported that the fuel injector nozzles were cleaned as part of the annual inspection. It is likely that at some point after removing the inserts or restrictors for cleaning, they were not reinstalled. Operational testing of the fuel injector nozzles without inserts or restrictors revealed extensive leakage. Operational testing of a four-cylinder engine of the same manufacturer revealed that without inserts or restrictors installed in any cylinder, the engine produced about 7% less horsepower at full power when compared to a baseline run of the same engine with all inserts or restrictors installed. There were no other engine or engine systems discrepancies noted.

Acoustic analysis of the engine indicated that, as the airplane became airborne and immediately before impact, the engine was operating about 2,400 rpm, which was about 11% less than the maximum continuous power setting of 2,700 rpm. Although the engine rpm at the start of the takeoff could not be determined from the available evidence, based on the postaccident engine testing and the extended ground roll distance, it was likely at a significantly decreased value, consistent with the 2,400 rpm recorded during two separate points later during the flight.

The mechanic likely incorrectly identified the maximum rpm value obtained during the postmaintenance engine run as falling within the normal operating range, and he did not recognize that with a constant-speed propeller installed the maximum full-power static rpm was specified to be within 50 rpm of the full-power value of 2,700 rpm. As such, the airplane should not have been returned to service.

The flight instructor and the pilot under instruction likely did not recognize during the takeoff roll that the engine was producing about 2,400 rpm instead of the normal 2,700 rpm. They also should have recognized that the ground run was excessive and aborted the takeoff while still on the runway. A witness reported that shortly after takeoff, when the airplane was about 25 ft above the runway, he heard a power reduction followed by a power advance. It is possible that the pilots initiated a rejected takeoff but chose to continue the flight, likely due to the limited remaining runway available for landing.

Probable Cause: Improper maintenance of the fuel injector nozzles and the pilots’ failure to abort the takeoff during the takeoff roll. Contributing to the accident was the mechanic’s decision to return the airplane to service with the engine unable to attain its full rated power.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA23FA033
Status: Investigation completed
Duration: 1 year and 7 months
Download report: Final report

Sources:

https://edition.cnn.com/2022/10/22/us/keene-new-hampshire-plane-crash/index.html
https://abc7chicago.com/new-hampshire-plane-crash-fatal-deadly/12360420/
https://www.nbcboston.com/news/local/plane-crashes-into-building-in-nh/2870286/
https://www.news10.com/news/northeast-news/new-hampshire-plane-crash-building-fire-under-investigation/
https://www.msn.com/en-us/video/news/lights-sound-of-fiery-nh-plane-crash-caught-on-camera/vi-AA13fheg?t=39
https://keenenh.gov/airport/10-21-2022-airplane-accident-information

https://data.ntsb.gov/Docket?ProjectID=106175

Location

Images:


Photo: NTSB

Media:

Revision history:

Date/timeContributorUpdates
22-Oct-2022 02:04 Geno Added
22-Oct-2022 06:28 harro Updated [Aircraft type, Source]
22-Oct-2022 06:33 harro Updated [Total fatalities, Total occupants, Location, Source]
22-Oct-2022 07:30 RobertMB Updated [Time, Aircraft type, Registration, Cn, Operator, Other fatalities, Location, Phase, Nature, Departure airport, Destination airport, Source, Embed code, Narrative]
22-Oct-2022 09:42 harro Updated [Aircraft type, Registration, Cn, Source, Embed code, Narrative]
22-Oct-2022 13:35 johnwg Updated [Time, Aircraft type, Registration, Cn, Source, Category]
22-Oct-2022 13:50 RobertMB Updated [Source, Narrative]
22-Oct-2022 13:59 RobertMB Updated [Aircraft type, Narrative]
22-Oct-2022 15:45 harro Updated [Aircraft type, Registration, Cn, Source, Narrative]
22-Oct-2022 19:34 harro Updated [Registration, Cn, Operator, Phase, Departure airport, Destination airport, Source, Narrative]
04-Nov-2022 00:03 Captain Adam Updated [Time, Location, Destination airport, Source, Narrative]
31-May-2024 12:20 Captain Adam Updated [Phase, Source, Narrative, Accident report, Photo]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org