NTSB Recommends Changes In Crew Scheduling, Comm Procedures After RJ Overrun | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

** AIRBORNE 06.18.13 Aero-TV-- CLICK HERE! ** HD iPad-Friendly Version -- AIRBORNE 06.18.13 **

** AIRBORNE 06.14.13 Aero-TV-- CLICK HERE! ** HD iPad-Friendly Version -- AIRBORNE 06.14.13**

** AIRBORNE 04.01.13 SPECIAL EDITION of Aero-TV-- CLICK HERE! ** HD iPad-Friendly Version -- AIRBORNE 04.01.13 SPECIAL EDITION **

Wed, Jun 18, 2008

NTSB Recommends Changes In Crew Scheduling, Comm Procedures After RJ Overrun

Lessons To Be Learned From April 2007 Incident At TVC

In the aftermath of the National Transportation Safety Board's review last week of the circumstances leading to the April 2007 runway overrun of a Pinnacle Airlines CRJ200 at Traverse City, MI, on Tuesday the NTSB issued three recommendations to the FAA intended to address crew fatigue issues, and other factors which may have contributed to the accident.

As ANN reported, on April 12, 2007, about 0043 eastern daylight time, a Bombardier/Canadair Regional Jet (CRJ) CL600-2B19, N8905F, operated as Pinnacle Airlines flight 4712, ran off the departure end of runway 28 following a landing in snowy weather at Cherry Capital Airport (TVC), Traverse City, Michigan. There were no injuries among the 49 passengers and three crewmembers, though the aircraft was substantially damaged. The airplane had departed from Minneapolis-St. Paul International Airport (MSP) about 2153 central daylight time (CDT).

The National Transportation Safety Board determined that the probable cause of this accident was the pilots’ decision to land at TVC without performing a landing distance assessment, which was required by company policy because of runway contamination initially reported by TVC ground operations personnel and continuing reports of deteriorating weather and runway conditions during the approach.

"This poor decision-making likely reflected the effects of fatigue produced by a long, demanding duty day, and, for the captain, the duties associated with check airman functions," the NTSB determined.

Contributing to the accident were the FAA pilot flight and duty time regulations that permitted the pilots’ long, demanding duty day, and the TVC operations supervisor’s use of ambiguous and unspecific radio phraseology in providing runway braking information.

The NTSB determined the FAA should:

  • Emphasize with principal operations inspectors the importance of conducting timely postaccident drug and alcohol testing. (A-08-40) (Editor's Note -- In its full report, the NTSB states there's no reason to suspect either pilot was impaired by alcohol... but notes due to the lack of requirements for the pilots to be tested immediately following the accident, no determination can be made.)
  • As part of the Takeoff/Landing Performance Assessment Aviation Rulemaking Committee, address the need for initial training on the rationale for and criticality of conducting landing distance assessments before landing on contaminated runways. (A-08-41)
  • Issue a CertAlert to all 14 Code of Federal Regulations Part 139 certificated airports that describes the circumstances of this accident, emphasizes the importance of specific and decisive radio communications, and urges airports to ensure that those criteria are being met in all airfield radio communications. (A-08-42)
  • Require all 14 Code of Federal Regulations Part 139 certificated airport operators to include in their airport's snow and ice control plan absolute criteria for type and depth of contamination and runway friction assessments that, when met, would trigger immediate closure of the affected runway to air carrier operations. Friction assessments should be based on pilot braking action reports, values obtained from ground friction measuring equipment, or estimates provided by airport ground personnel. (A-08-43)

The NTSB also reaffirmed its position the FAA adhere to three previous recommendations:

  • Evaluate crash detection and location technologies, select the most promising candidate(s) for ensuring that emergency responders could expeditiously arrive at an accident scene, and implement a requirement to install and use the equipment. (A-01-66)
  • Immediately require all 14 Code of Federal Regulations Part 121, 135, and 91 subpart K operators to conduct arrival landing distance assessments before every landing based on existing performance data, actual conditions, and incorporating a minimum safety margin of 15 percent. (A-07-57) (Urgent)
  • Modify and simplify the flight crew hours-of-service regulations to take into consideration factors such as length of duty day, starting time, workload, and other factors shown by recent research, scientific evidence, and current industry experience to affect crew alertness. (A-06-10)
FMI: Read The NTSB's Complete Recommendations (.pdf)

Advertisement

More News

Classic Aero-TV: Bob 'Mister FBO' Showalter -- Examining The Future Of Aviation

A True Aviation Pioneer Talks About The Future of GA Originally Webcast, 05.30.12: Even to many who have to compete with him, Bob Showalter is "Mr. FBO." A veteran of decades of se>[...]

AgustaWestland Displays Project Zero Tilt Rotor At Le Bourget

Electric VTOL Aircraft Is Turning Heads In France Among the thousands of aircraft and products on display at the Paris Air Show getting a lot of attention this week is one that may>[...]

ANN's Daily Aero-Linx (06.20.13)

Professional Helicopter Pilots Association This website provides valuable information to helicopter operators, including quick access to TFR maps, Homeland Security bulletins, form>[...]

ANN's Daily Aero-Term (06.20.13): Warm Advection

Transport of warm air into an area by horizontal winds. Low-level warm advection sometimes is referred to (erroneously) as overrunning. Although the two terms are not properly inte>[...]

Aero-News: Quote Of The Day (06.20.13)

“We have clearly heard the voice of scientists and their unanimous recommendations to change the proposal. From now on, nobody can claim ‘We did not know’." Sourc>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

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