ASN Wikibase Occurrence # 300369
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: | Monday 31 October 2022 |
| Time: | 13:04 |
| Type: |  Beechcraft G58 Baron |
| Owner/operator: | Cohen Aircraft Leasing & Sales LLC |
| Registration: | N495AU |
| MSN: | TH-2287 |
| Year of manufacture: | 2010 |
| Total airframe hrs: | 756 hours |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | near Alpharetta, GA -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Jekyll Island Airport, GA (09J) |
| Atlanta-DeKalb Peachtree Airport, GA (PDK/KPDK) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Information verified through data from accident investigation authorities |
On October 31, 2022, at 1304 eastern daylight time, a Hawker Beechcraft G58 airplane, N495AU, was destroyed when it was involved in an accident in Alpharetta, Georgia. The pilot and a passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
Preliminary air traffic control and radar information provided by the Federal Aviation Administration (FAA) indicated that the airplane departed from Jekyll Island Airport (09J), Jekyll Island, Georgia at 1152 with an intended destination of DeKalb-Peachtree Airport (PDK), Atlanta, Georgia. The airplane was being vectored for the ILS (instrument landing system) or LOC (localizer) RWY 21L instrument approach to PDK. When the airplane was about 5 miles from the final approach fix, an air traffic controller issued an approach clearance and instructed the pilot to turn left to a heading of 240° and maintain 3,000 ft mean sea level (msl) until established on the localizer; however, the pilot did not readback the altitude in the clearance. The controller again instructed the pilot to maintain 3,000 ft until established on the localizer and re-stated the approach clearance. The pilot acknowledged with the airplane’s call sign only. The airplane then climbed to 3,200 ft msl before it began to descend. An air traffic controller received a minimum safe altitude warning (MSAW) alert when the airplane descended through 2,400 ft msl, and immediately instructed the pilot to check the airplane’s altitude and to start climbing. The pilot responded that he was climbing and “going around.” The controller instructed the pilot to climb to 3,000 ft, turn to 330°, and to keep “wings level.” The pilot read back the instructions. The airplane then initiated a climbing right turn to 3,200 ft msl, before it made a descending left turn. The controller continued to receive MSAW alerts and made numerous attempts to contact the pilot, but there was no further communication with him. The airplane continued to descend, until it was no longer observed on radar. The last radar return was received at 1304:19. At that time, the airplane was at an altitude of 1,325 ft msl (about 355 above ground level), heading 252°, at a ground speed of 215 knots.
A witness was walking home when he heard the airplane. He said the engine(s) sounded Page 2 of 3 “powerful and even, with no sputtering or skipping.” The witness looked up but was initially unable to see the airplane due to the “heavy” and low cloud cover. When the airplane crossed directly in front of him (right to left), it exited the cloud cover. The wings were level and there was no smoke, fire, or anything trailing behind the airplane. The nose of the airplane was pointed “slightly” down toward the ground, and it was moving “very fast”. The airplane continued to descend under high engine power before it impacted the ground. He further stated, “At no time did I see or hear any change in engine power, angle of descent or direction of travel. The aircraft simply flew into the ground, with no visible attempt by the pilot to turn or pull up.”
The airplane impacted wooded terrain on a magnetic heading of 252° about 16 miles northwest of PDK. The initial impact point was a stand of approximately 60-ft-tall trees. The cuts on the trees became progressively lower before it impacted the ground. Numerous pieces of angular cut wood were located along the wreckage path.
The airplane impacted the ground and was heavily fragmented consistent with a high energy impact. Both engines were buried about 4 ft in the ground. The airplane’s seats and portions of the cockpit were also located in the impact crater with the engines.
Fragmented sections of the airplane’s wings, fuselage and tail section were found around and forward of the main wreckage. All major components of the airplane were located at the accident site. There was no post-impact fire.
The wreckage was recovered and retained for further investigation.
Sources:
https://news.yahoo.com/couple-killed-alpharetta-plane-crash-213544557.html
https://www.macon.com/news/state/georgia/article268129317.html
https://www.forsythnews.com/news/public-safety/alpharetta-authorities-responding-plane-crash-near-big-creek-greenway/
NTSB
https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=495AU
https://globe.adsbexchange.com/?icao=a622be&lat=34.049&lon=-84.271&zoom=14.0&showTrace=2022-10-31
https://www.wsbtv.com/news/local/no-survivors-after-small-plane-crashes-big-creek-greenway-alpharetta/IYHIKPBSKFHR7EFRBAWGPXISGA/
https://www.jetphotos.com/photo/10346771 (photo)
Location
Media:
NTSB is investigating the Oct. 31 crash of a Beech BE58 near Alpharetta, Georgia.
— NTSB Newsroom (@NTSB_Newsroom) October 31, 2022
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 31-Oct-2022 19:16 | Captain Adam | Added |
| 31-Oct-2022 19:40 | nhofmann54 | Updated [Time, Aircraft type, Registration, Cn, Operator, Other fatalities, Phase, Departure airport, Source, Embed code] |
| 31-Oct-2022 19:41 | harro | Updated [Narrative] |
| 31-Oct-2022 20:13 | mt3 | Updated [Registration, Phase, Destination airport] |
| 31-Oct-2022 20:49 | nhofmann54 | Updated [Total fatalities, Total occupants, Source, Narrative] |
| 01-Nov-2022 02:04 | johnwg | Updated [Time, Aircraft type, Operator, Location, Phase, Nature, Source, Narrative, Category] |
| 01-Nov-2022 16:00 | mt3 | Updated [Total fatalities, Source, Narrative] |
| 01-Nov-2022 16:47 | RobertMB | Updated [Aircraft type, Operator, Phase, Source, Narrative] |
| 01-Nov-2022 18:43 | RobertMB | Updated [Total fatalities, Total occupants, Source] |
| 02-Nov-2022 01:28 | johnwg | Updated [Aircraft type, Phase, Narrative] |
| 03-Nov-2022 17:55 | mt3 | Updated [Phase, Source, Narrative] |
| 04-Nov-2022 14:31 | mt3 | Updated [Total fatalities, Total occupants, Source, Narrative] |
| 04-Nov-2022 22:50 | RobertMB | Updated [Aircraft type, Narrative] |
| 15-Nov-2022 12:27 | Anon. | Updated [Aircraft type, Phase, Source, Narrative] |
| 17-Nov-2022 22:40 | Ron Averes | Updated [Aircraft type] |
| 18-Nov-2022 19:50 | Captain Adam | Updated [Time, Source, Narrative] |
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