JetBlue Tail Strike at Yampa Valley (KHDN)
Thread Starter
JetBlue Tail Strike at Yampa Valley (KHDN)
1/22/22, noon local, JetBlue A320 (N760JB) incurs a tail strike due to early rotation to avoid an opposite-direction King Air 350 (N350J). KHDN is a non-controlled airport. N350J approaching from east, initially IFR with plan to land runway 10. JetBlue departs gate, planning to depart runway 10. King Air cancels IFR and changes plan to land runway 28. Despite talking to each other on CTAF, both aircraft end up nose-to-nose and expensive comedy ensues.
Some additional info:
Prior to V1 (near 80 knots), both JB pilots acknowledged that the King Air was landing opposite direction and did not have the King Air in sight, yet did not reject the takeoff.
According to a ground witness, the weather was clear. However, there was a localized layer of fog directly over the AWOS sensor, causing the AWOS to report 500 overcast. Did this cause the JB crew to believe Denver Center would deconflict their departure as the airport was reporting IFR weather?
According to the JB crew, Denver Center was “extremely busy.” When finally able to establish contact, the JB crew was given a 2-minute release window.
From the JB CVR, the King Air made 4 CTAF announcements indicating landing on runway 28 (but never using the word “runway”). JB made 3 CTAF announcements indicating departure on runway 10. The final King Air CTAF transmission was “all right we’re on short final, I hope you don’t hit us.”
NTSB Final Report - N760JB
Some additional info:
Prior to V1 (near 80 knots), both JB pilots acknowledged that the King Air was landing opposite direction and did not have the King Air in sight, yet did not reject the takeoff.
According to a ground witness, the weather was clear. However, there was a localized layer of fog directly over the AWOS sensor, causing the AWOS to report 500 overcast. Did this cause the JB crew to believe Denver Center would deconflict their departure as the airport was reporting IFR weather?
According to the JB crew, Denver Center was “extremely busy.” When finally able to establish contact, the JB crew was given a 2-minute release window.
From the JB CVR, the King Air made 4 CTAF announcements indicating landing on runway 28 (but never using the word “runway”). JB made 3 CTAF announcements indicating departure on runway 10. The final King Air CTAF transmission was “all right we’re on short final, I hope you don’t hit us.”
NTSB Final Report - N760JB
