Home
Forums
New posts
Search forums
What's new
New posts
Latest activity
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Home
Forums
Brown Cafe UPS Forum
UPS Discussions
Amazon Prime cargo plane crashes
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="worldwide" data-source="post: 3966084" data-attributes="member: 2193"><p>A tragic crash for Atlas - RIP to the crew.</p><p></p><p>The NTSB came to a different conclusion as to the probable cause of the Birmingham crash versus your false post about the crew working "24 hours straight or whatever." Fatigue was a contributing factor but the crew did not work "24 hours." No doubt working on the backside of the clock is challenging and can mess with your circadian rhythm but the NTSB was more focused on the Captain's previous training records and how he reacted during the approach. The training records for the captain of that flight indicated past performance deficiencies that are consistent with the types of errors made during the accident flight.</p><p></p><p>"During this flight, the captain demonstrated poor decision-making by continuing the approach after the profile did not capture, failing to communicate the change in the approach method, not monitoring the descent rate and altitude, and failing to initiate a go-around when the approach was unstabilized below 1,000 ft. The NTSB concludes that the captain’s poor performance during the accident flight was consistent with past performance deficiencies in flying non-precision approaches noted during training; the errors that the captain made were likely the result of confusion over why the profile did not engage, his belief that the airplane was too high, and his lack of compliance with SOPs."</p><p></p><p>On September 9, 2014 the National Transportation Safety Board announced that <strong>the probable cause of the accident was that the aircrew had made an unstabilized approach into Birmingham-Shuttlesworth International Airport during which they failed to adequately monitor their altitude</strong>. The aircraft descended below the minimum descent altitude when the runway was not yet in sight, resulting in <a href="https://en.wikipedia.org/wiki/Controlled_flight_into_terrain" target="_blank">controlled flight into terrain</a> approximately 3,300 feet short of the runway threshold. The NTSB also found that contributing factors in the accident were:</p><p></p><ol> <li data-xf-list-type="ol">the flight crew’s failure to properly configure and verify the flight management computer for the profile approach;</li> <li data-xf-list-type="ol">the captain’s failure to communicate his intentions to the first officer once it became apparent the vertical profile was not captured;</li> <li data-xf-list-type="ol">incomplete weather information that led the flight crew to expect they would break out of cloud at 1,000 feet above ground level;</li> <li data-xf-list-type="ol">the first officer’s failure to make the required minimums callouts;</li> <li data-xf-list-type="ol">the captain’s performance deficiencies, likely due to factors including, but not limited to, fatigue, distraction, or confusion, consistent with performance deficiencies exhibited during training, and;</li> <li data-xf-list-type="ol">the first officer’s fatigue due to acute sleep loss resulting from her ineffective off-duty time management.</li> </ol><p>Source: <a href="https://www.ntsb.gov/investigations/AccidentReports/Reports/AAR1402.pdf" target="_blank">https://www.ntsb.gov/investigations/AccidentReports/Reports/AAR1402.pdf</a></p></blockquote><p></p>
[QUOTE="worldwide, post: 3966084, member: 2193"] A tragic crash for Atlas - RIP to the crew. The NTSB came to a different conclusion as to the probable cause of the Birmingham crash versus your false post about the crew working "24 hours straight or whatever." Fatigue was a contributing factor but the crew did not work "24 hours." No doubt working on the backside of the clock is challenging and can mess with your circadian rhythm but the NTSB was more focused on the Captain's previous training records and how he reacted during the approach. The training records for the captain of that flight indicated past performance deficiencies that are consistent with the types of errors made during the accident flight. "During this flight, the captain demonstrated poor decision-making by continuing the approach after the profile did not capture, failing to communicate the change in the approach method, not monitoring the descent rate and altitude, and failing to initiate a go-around when the approach was unstabilized below 1,000 ft. The NTSB concludes that the captain’s poor performance during the accident flight was consistent with past performance deficiencies in flying non-precision approaches noted during training; the errors that the captain made were likely the result of confusion over why the profile did not engage, his belief that the airplane was too high, and his lack of compliance with SOPs." On September 9, 2014 the National Transportation Safety Board announced that [B]the probable cause of the accident was that the aircrew had made an unstabilized approach into Birmingham-Shuttlesworth International Airport during which they failed to adequately monitor their altitude[/B]. The aircraft descended below the minimum descent altitude when the runway was not yet in sight, resulting in [URL='https://en.wikipedia.org/wiki/Controlled_flight_into_terrain']controlled flight into terrain[/URL] approximately 3,300 feet short of the runway threshold. The NTSB also found that contributing factors in the accident were: [LIST=1] [*]the flight crew’s failure to properly configure and verify the flight management computer for the profile approach; [*]the captain’s failure to communicate his intentions to the first officer once it became apparent the vertical profile was not captured; [*]incomplete weather information that led the flight crew to expect they would break out of cloud at 1,000 feet above ground level; [*]the first officer’s failure to make the required minimums callouts; [*]the captain’s performance deficiencies, likely due to factors including, but not limited to, fatigue, distraction, or confusion, consistent with performance deficiencies exhibited during training, and; [*]the first officer’s fatigue due to acute sleep loss resulting from her ineffective off-duty time management. [/LIST] Source: [URL]https://www.ntsb.gov/investigations/AccidentReports/Reports/AAR1402.pdf[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Brown Cafe UPS Forum
UPS Discussions
Amazon Prime cargo plane crashes
Top