NTSB Prelim: Bombardier Inc CL-600-2B16 | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Most Recent Daily Episodes

Episode Date

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday Airborne-Thursday

Airborne-Friday

Airborne On YouTube

Airborne-Unlimited-04.29.24

Airborne-NextGen-04.30.24

Airborne-Unlimited-05.01.24 Airborne-AffordableFlyers--05.02.24

Airborne-Unlimited-05.03.24

Sun, Aug 22, 2021

NTSB Prelim: Bombardier Inc CL-600-2B16

Requested To Circle To Runway 11 For The Longer Runway

Location: Truckee, CA Accident Number: WPR21FA286
Date & Time: July 26, 2021, 13:18 Local Registration: N605TR
Aircraft: BOMBARDIER INC CL-600-2B16 Injuries: 6 Fatal
Flight Conducted Under: Part 91: General aviation - Personal

On July 26, 2021, about 1318 Pacific daylight time, a Bombardier Inc., CL-600-2B16 airplane, N605TR, was destroyed when it was involved in an accident near Truckee, California. The pilot, copilot and 4 passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to automatic dependent surveillance-broadcast (ADS-B) data and preliminary air traffic control (ATC) audio from the Federal Aviation Administration, the airplane departed Coeur d’Alene, Idaho, about 1145 and made a left turn to the south. The flight crew was in contact with ATC throughout the duration of the flight. As the airplane was passing over northwestern Nevada, ATC began issuing descent instructions for the airplane’s approach into Truckee-Tahoe Airport (TRK). Once the airplane descended below 26,000 ft, ATC advised the flight crew to expect the RNAV (GPS) Runway 20 approach at TRK. The flight crew accepted the approach but requested to circle to runway 11 for the longer runway and the controller told them to expect the circling approach.

After coordinating with the TRK tower, the controller informed the flight crew that they would be number two for TRK and could expect some delays. ATC then cleared the airplane to hold north of the ALVAA waypoint, the initial approach fix to the RNAV runway 20 approach. After one turn in holding, ATC cleared the airplane for the RNAV runway 20 approach, cancelled radar services, and instructed the pilot to contact the TRK tower. The flight crew established communication with the TRK tower controller when they were near the LUMMO waypoint, located about 9.6 nm north of the approach end of runway 20. The tower controller offered the flight crew the option of crossing over the field and enter the left downwind leg for runway 29 or to enter downwind leg for runway 11. Once the flight crew announced they were making a right turn and reported runway 11 in sight, the controller then cleared them to land on runway 11 and informed them that the airplane was not in sight. The flight crew Multiple eyewitnesses observed the airplane before the crash. Some reported that the airplane caught their attention because of its low altitude and abnormal flight path into runway 11. According to witnesses, the airplane was in a nose down attitude and steep left turn during its last few seconds of flight. A witness located about 50 ft from the accident site reported that he observed the airplane come from the northwest about 20 ft above the trees. The airplane then entered a steep left turn and banked erratically just before it impacted trees and then the ground. The witnesses close to the accident site stated that the airplane appeared intact when they first observed it.

Three surveillance videos captured the accident flight’s final movements and were all consistent with the witness’ recounts. The accident site was located on a hillside between a golf course fairway and a residential street. The airplane was consumed by postcrash fire. A debris path, which measured about 225 ft long and 85 ft wide was marked by several broken trees and was oriented on an easterly heading. The initial point of impact was identified by a severed tree that stood about 70 ft tall, located about 120 ft west of the main wreckage. Portions of the right and left wings and control surfaces were found fragmented along the debris path. Additional airframe fragments were collocated with the main wreckage, which was comprised of both engines, the empennage, and fuselage remnants.

According to FAA regulations, the airplane was required to have, at a minimum, a 30-minute Cockpit Voice Recorder (CVR) and an 18 parameter Flight Data Recorder (FDR). The airplane was equipped with recorders that exceeded these requirements. The FDR and CVR were recovered and were successfully read out by the NTSB’s Vehicle Recorder Lab, and the data is being analyzed.

FMI: www.ntsb.gov

Advertisement

More News

ANN's Daily Aero-Term (05.01.24): Say Altitude

Say Altitude Used by ATC to ascertain an aircraft's specific altitude/flight level. When the aircraft is climbing or descending, the pilot should state the indicated altitude round>[...]

ANN's Daily Aero-Linx (05.01.24)

Aero Linx: European Air Law Association (EALA) EALA was established in 1988 with the aim to promote the study of European air law and to provide an open forum for those with an int>[...]

Classic Aero-TV: Korean War Hero Twice Reborn

From 2023 (YouTube Version): The Life, Death, Life, Death, and Life of a Glorious Warbird In 1981, business-owner Jim Tobul and his father purchased a Chance-Vought F4U Corsair. Mo>[...]

Airborne 04.29.24: EAA B-25 Rides, Textron 2024, G700 Deliveries

Also: USCG Retires MH-65 Dolphins, Irish Aviation Authority, NATCA Warns FAA, Diamond DA42 AD This summer, history enthusiasts will have a unique opportunity to experience World Wa>[...]

Airborne Affordable Flyers 05.02.24: Bobby Bailey, SPRG Report Cards, Skydive!

Also: WACO Kitchen Bails, French SportPlane Mfr to FL, Dynon-Advance Flight Systems, Innovation Preview Bobby Bailey, a bit of a fixture in sport aviation circles for his work with>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2024 Web Development & Design by Pauli Systems, LC