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: | Wednesday 5 October 2022 |
| Time: | 13:56 |
| Type: |  Beechcraft A36AT Bonanza |
| Owner/operator: | ABET |
| Registration: | N902AT |
| MSN: | E-2623 |
| Year of manufacture: | 1991 |
| Total airframe hrs: | 3953 hours |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Arundel, ME -
 United States of America
|
| Phase: | Approach |
| Nature: | Executive |
| Departure airport: | Presque Isle International Airport, ME (PQI/KPQI) |
| Biddeford Municipal Airport, ME (B19) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
On October 5, 2022, about 1356 eastern daylight time, a Beech A36, N902AT, was destroyed when it was involved in an accident near Arundel, Maine. The private pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 business flight.
The pilot and passenger departed on an instrument flight rules (IFR) cross-country flight to the pilot’s home airport at the conclusion of a business trip. Weather radar imagery superimposed over the airplane’s flight track indicated that the airplane was flying toward an area of light intensity echoes associated with light rain to drizzle and instrument meteorological conditions as it approached the area of the destination airport. An AIRMET advisory for these conditions, as well as low-level turbulence, was valid for the accident time.
The pilot confirmed to the controller that he had obtained the most recent weather information at the destination and requested the RNAV (GPS) instrument approach procedure. The nearest airport with recorded weather observations, about 11 nautical miles west of the destination airport, reported 2.5 miles visibility, a broken cloud ceiling at 700 ft above ground level (agl), and an overcast ceiling at 1,000 ft agl about the time of the accident.
When provided vectors to the final approach course, and when issued his approach clearance, the pilot’s acknowledgements and read-backs of controller instructions were delayed by several seconds and incomplete. Automatic dependent surveillance – broadcast (ADS-B) track data indicated that the airplane flew through, then turned left toward, the final approach course. About 30 seconds after crossing the initial approach fix, about 200 ft below the minimum altitude, the controller issued the pilot a frequency change and provided a phone number through which to cancel his IFR clearance once on the ground. As the airplane proceeded parallel to and east of the final approach course, it continued to descend, and remained consistently hundreds of feet below the minimum published altitude for each respective segment of the approach. The airplane passed the final approach fix 750 ft below the minimum altitude at 58 knots groundspeed. The airplane continued to descend over the next .75 miles at a ground speed about 60 kts before the data ended in the vicinity of the accident site.
Several witnesses below the airplane’s flight path reported hearing the airplane, but stated that they could not see the airplane due to the low clouds, rain, and fog at the time of the accident. Their descriptions of the engine sound varied from “not normal” to “didn’t sound healthy” to sounding “…usual, just lower and louder.”
Examination of the accident site revealed severed tree trunks with clean, angular cuts, consistent with the engine producing power at the time of impact. Examination of the wreckage, as well as an engine test run, revealed no pre-impact mechanical anomalies that would have precluded normal operation.
About 8 months before the accident, the airplane was equipped with dual electronic flight instruments that functioned as the primary attitude indicator and directional gyro. These instruments were integrated with the airplane’s existing autopilot system. Review of the pilot’s logbook indicated that, after receiving about 2 hours of dual instruction, he had flown the airplane about 34 hours since the installation of the avionics, of which 7 hours was recorded as actual IFR
The instrument meteorological conditions the pilot encountered during the approach to the destination airport would have resulted in a loss of outside visual references, requiring the pilot to rely on the flight instruments to maintain his intended course, altitude, and airspeed. The instrument conditions, likely turbulence, and increased workload imposed by beginning the approach phase of the flight presented a situation that was conducive to the development of spatial disorientation and a loss of situational awareness. Given that the pilot maintained a position east of the final approach course for most of the approach and far below the minimum published altitude throughout the approach, it is likely that he had lost situational awareness of the airplane’s position. No information was available to determine the modes or settings of the avionics and/or autopilot during the approach. Whether the pilot’s familiarity with the relatively new avionics and their interface with the autopilot contributed to the accident could not be determined based on the available information.
Probable Cause: The pilot’s loss of situational awareness, which resulted in an unstabilized approach, descent below published minimum altitudes, and collision with terrain.
Accident investigation:
 |
|
Sources:
https://www.sunjournal.com/2022/10/05/plane-crashes-in-arundel-near-route-1/
https://www.bostonglobe.com/2022/10/05/metro/single-engine-plane-goes-down-arundel-maine/
https://www.newscentermaine.com/article/news/local/crews-respond-to-plane-crash-in-arundel-maine-sams-road-biddeford/97-d1527b3a-5185-4d79-921c-8275fe2308f5
https://www.wmtw.com/article/plane-crashes-in-york-county-maine/41535109
https://data.ntsb.gov/Docket?ProjectID=106070
https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=902AT
https://flightaware.com/live/flight/N902AT/history/20221005/1615Z/KPQI/B19
Location
Images:
Photo: NTSB
Media:
NTSB investigating today's crash of a Beech 36 airplane in Arundel, Maine.
— NTSB Newsroom (@NTSB_Newsroom) October 5, 2022
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 05-Oct-2022 19:48 | Geno | Added |
| 06-Oct-2022 01:46 | RobertMB | Updated [Time, Aircraft type, Registration, Cn, Operator, Total fatalities, Total occupants, Other fatalities, Location, Phase, Nature, Departure airport, Destination airport, Source, Embed code, Damage, Narrative] |
| 06-Oct-2022 01:47 | RobertMB | Updated [Embed code, Narrative] |
| 06-Oct-2022 02:59 | Captain Adam | Updated [Location, Source, Narrative, Category] |
| 06-Oct-2022 04:12 | RobertMB | Updated [Location, Narrative] |
| 06-Oct-2022 04:41 | RobertMB | Updated [Narrative] |
| 21-Oct-2022 18:46 | Captain Adam | Updated [Time, Location, Nature, Source, Narrative, Category] |
| 13-Jun-2024 15:25 | Captain Adam | Updated [Source, Narrative, Accident report, Photo] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation