Author Topic: UPS A300 crash at Birmingham, AL  (Read 17416 times)

Offline notaperfectpilot

  • Full Member
  • ***
  • Posts: 243
  • PPL
UPS A300 crash at Birmingham, AL
« on: August 14, 2013, 08:46:39 AM »
happened this morning, apparently touched down a mile before the runway. Unfortunately there isn't a LiveATC feed for BHM, so no audio to post...

AvHerald article

http://avherald.com/h?article=466d969f&opt=0

and CNN

http://www.cnn.com/2013/08/14/us/alabama-cargo-plane-crash/index.html?eref=rss_mostpopular

Apparently the crew has died, RIP.



Offline kd4moj

  • Newbie
  • *
  • Posts: 27
Re: UPS A300 crash at Birmingham, AL
« Reply #1 on: August 14, 2013, 09:06:39 AM »
that's terrible... just heard it on the news...

...DOUG
KD4MOJ
KTLH Feeder
WWW.KD4MOJ.ORG
WWW.KTLH.NET

Offline joeyb747

  • Hero Member
  • *****
  • Posts: 1627
  • Nothing Like A 747!
Re: UPS A300 crash at Birmingham, AL
« Reply #2 on: August 18, 2013, 07:34:10 PM »
"In their fourth and last press conference on Aug 17th the NTSB reported, the flight data recorder data have been validated. First results suggests the flight control inputs and flight control surface movements correlate, the engine parameters were normal. The flight data recorder stopped a few seconds prior to the cockpit voice recorder. The autopilot was engaged until the end of flight data recording end, the speed was about 140 KIAS as selected by the autoflight system consistent with the expected approach speed. The flight data recorder also confirmed the Sinkrate GPWS alerts. A checkflight by FAA on the PAPI system confirmed the PAPIs were indicating correctly to 1/100th of a degree. The aircraft had been updated to comply with all service bulletins and airworthiness directives."

From the updated AvHerald article. Also several new pictures accompany the article...
Aircraft Mechanic

Offline ORD Don

  • Full Member
  • ***
  • Posts: 139
Re: UPS A300 crash at Birmingham, AL
« Reply #3 on: August 21, 2013, 12:29:03 PM »




                 Does anybody have any ideas ?    Or is it way too early to tell.

Offline w0x0f

  • Sr. Member
  • ****
  • Posts: 342
Re: UPS A300 crash at Birmingham, AL
« Reply #4 on: August 21, 2013, 12:56:14 PM »
Here is a 14 year old NASA ASRS report regarding the LOC RWY 18 approach to BHM.  The first sentence now seems to be prophetic.

http://www.37000feet.com/report/437033/F10-crew-concerned-about-proximity-to-terrain-on-approach-to-runway-18

w0x0f

Offline notaperfectpilot

  • Full Member
  • ***
  • Posts: 243
  • PPL
Re: UPS A300 crash at Birmingham, AL
« Reply #5 on: August 21, 2013, 01:06:50 PM »
Here is a 14 year old NASA ASRS report regarding the LOC RWY 18 approach to BHM.  The first sentence now seems to be prophetic.

http://www.37000feet.com/report/437033/F10-crew-concerned-about-proximity-to-terrain-on-approach-to-runway-18

w0x0f

indeed it does. Is it possible that the crew was indeed right on the PAPI, and they clipped some trees on the hill? The GPWS alert could have been generated just from the descent rate + rising terrain.  The way I read that ASRS report, it could be entirely possible that they were slightly low on the PAPI, but not low enough to show a big light change, and still hit trees. (plus remember tree growth, the report was written 14 years ago, they could be higher now)

Offline ORD Don

  • Full Member
  • ***
  • Posts: 139
Re: UPS A300 crash at Birmingham, AL
« Reply #6 on: August 22, 2013, 11:11:15 AM »
Here is a 14 year old NASA ASRS report regarding the LOC RWY 18 approach to BHM.  The first sentence now seems to be prophetic.

http://www.37000feet.com/report/437033/F10-crew-concerned-about-proximity-to-terrain-on-approach-to-runway-18

w0x0f


              VERY interesting (and sad)....     thank you

Offline derg

  • Newbie
  • *
  • Posts: 8
Re: UPS A300 crash at Birmingham, AL
« Reply #7 on: August 23, 2013, 09:50:28 AM »
The PAPIS are set to a glide slope of 3.24 degrees. FAA did a test and found they were 1/100 of one degree out of alignment.  Yesterday they publish the glide slope as 3.20 degrees.  So they suddenly find four times the error? This is on the RNAV-GPS approach to 18. I really don't think anybody gives a damn.