Pasco-Tri-Cities

On September 20, 2022, about 0709 Pacific daylight time, a Cessna 525B, jet airplane, N528DV, was destroyed when it was involved in an accident near Pasco, Washington. The pilot and 9 passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 business flight. The pilot reported that the flight to Tri-Cities Airport, (PSC), Pasco, Washington, was uneventful; he reported to the tower controller that the airport was in sight and requested to land on runway 3L. While on left base, the pilot further reported that he started to lower the flaps and extended the gear handle. He did not recall confirming whether the gear was down and locked but reported that there were no landing caution annunciation or aural warnings. Before making contact with the runway, the pilot noticed that the airplane floated longer than expected and upon touchdown realized that the landing gear was not extended. The airplane slid down the runway and came to a stop near the departure end of the runway. The pilot secured the engines and assisted the passengers evacuate the airplane. During the evacuation, the pilot reported that the airplane was on fire near the right engine. Shortly thereafter, the airplane was engulfed in flames.

While approaching class B airspace, the airline transport pilot was in communication with a controller who later stated that the pilot's speech was slurred, and the controller repeatedly asked if the oxygen system on the airplane was working properly. As the airplane approached a nearby airport, about 85 miles from his destination airport, the pilot stated he had the airport in sight and repeatedly requested a visual approach. The controller instructed the pilot to continue his flight to his destination, in a southwest direction. As the controller attempted to maintain communications, the pilot dropped off radar shortly after passing the nearby airport and subsequently landed at the nearby airport, which was not his destination airport. According to a surveillance video and impact marks on the runway, the airplane landed hard about halfway down the runway and slid to a stop on the left side of the runway. The airplane fuselage and wings were mostly consumed by postimpact fire. After authorities arrived onsite, the pilot was arrested for operating an aircraft under the influence of alcohol. The pilot was found to have a blood alcohol level of .288, which likely contributed to the pilot landing at the incorrect airport and his subsequent loss of airplane control during landing.

The pilot received abbreviated weather briefing for emergency medical service (EMS)/air ambulance flight. Before flight, he expressed anxiety about possible low visibility for landing and timely transport of dying patient. During ILS runway 03 approach (rwy 03 approach), the aircraft remained well above the glide slope until close to the middle marker; aircraft's speed decreased from 153 to 100 kts, while vertical speed increased from 711 feet/min to about 1,250 feet/min descent. About 1 mile from runway and 500 feet agl (in fog), the aircraft abruptly turned left of localizer course and gradually descended with no distress call from pilot. The aircraft hit a pole, then flew into a building and burned. Low ceiling, fog and dark night conditions prevailed. Pilot (recent ex military helicopter pilot) had logged/reported 3,500 hours of flight time and about 150 hours in multiengine airplanes, but there was evidence he lacked experience with actual instrument approaches in fixed wing aircraft; he had difficulty with instrument flying during recent training and FAA check flights. No preimpact mechanical problem was found with aircraft/engines. No ILS anomalies were found. Flight nurse was using cellular phone, but no evidence was found of interference with aircraft's navigational system. Visibility and ceiling at destination were less than forecast at time of pilot's preflight weather briefing. Paramedic was only survivor.

During arrival for an ILS runway 21R approach, the aircraft encountered icing conditions for about 9-1/2 minutes. As the aircraft was vectored for the approach, the Seattle ARTCC controller used an expanded radar range and did not provide precise positioning of the aircraft to the final approach course. The flight crew attempted to continue on a steep, unstabilized approach for a landing. Recorded radar data showed that the aircraft was well to the right of the ILS course line and well above the glide slope as it passed the outer marker/final approach fix (faf). It did not intercept the localizer course until it was about 1.5 mile inside the faf. Also, it was still well above the ILS glide slope were recorded altitude data was lost when the aircraft was abt 2.5 miles from the airport. The tower had closed, but the controller saw the aircraft in a higher than normal rate of descent in a wings level attitude. Before reaching the runway, the aircraft nosed over and crashed in a steep descent. There was evidence that ice had accumulated on the airframe, including the horizontal stabilizers, which may have resulted in a tail plane stall. All six occupants were killed.