Incidente Birmingham - AL - USA (thread tecnico)

Area dedicata alla discussione sugli incidenti e degli inconvenienti aerei e le loro cause. Prima di intervenire in quest'area leggete con attenzione il regolamento specifico riportato nel thread iniziale

Moderatore: Staff md80.it

Rispondi
Avatar utente
albert
md80.it Staff
md80.it Staff
Messaggi: 5839
Iscritto il: 9 ottobre 2007, 2:16
Località: Liguria

Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da albert » 14 agosto 2013, 13:21

Alberto
MD80 Fan

«Ogni domanda alla quale si possa dare una risposta ragionevole è lecita.» Konrad Lorenz
«Un sogno scaturito da un grande desiderio: la grande voglia di volare e scoprire altri orizzonti verso i quali andare, con la voglia di nuovo. Per me questa è l'avventura.» Angelo D'Arrigo
«Non prendete la vita troppo sul serio, comunque vada non ne uscirete vivi.» Robert Oppenheimer

Avatar utente
steno1974
01000 ft
01000 ft
Messaggi: 115
Iscritto il: 26 novembre 2007, 22:02
Località: LIPB

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da steno1974 » 14 agosto 2013, 15:28

Immagine
Meglio portar pazienza che portar malta.
Un "buon" atterraggio è quando ti puoi allontanare, camminando, dall'aereo. Un "grande" atterraggio è quando l'aereo si può usare ancora.
Volare non è pericoloso. E' il precipitare ad esserlo.

Avatar utente
Toeloop
FL 250
FL 250
Messaggi: 2893
Iscritto il: 14 luglio 2007, 9:55
Località: Between KTEB and KCDW
Contatta:

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da Toeloop » 14 agosto 2013, 18:22

Guardando su flightaware sembra che la discesa, ad un certo punto, sia stata un pochino "irruenta" visto che hanno avuto un rateo di oltre 5500 piedi per minuto. Questo fermo restando che non ho idea di quanto possa essere attendibile, su questo, flightaware.

05:43AM 33.8230 -86.7190 206° Southwest 288 331 9,500 -3,960 Level FlightAware
05:44AM 33.7760 -86.7480 207° Southwest 275 316 5,500 -5,520 Descending FlightAware
05:44AM 33.7247 -86.7489 207° Southwest 278 320 2,600 -1,860 Descending Atlanta Center
05:45AM 33.6644 -86.7469 178° South 248 285 2,500 -420 Descending Atlanta Center
05:46AM 33.6206 -86.7456 178° South 200 230 1,800 -540 Descending Atlanta Center
05:47AM 33.5681 -86.7539 188° South 191 220 1,500 -300 Descending Atlanta Center
Immagine
Immagine

Avatar utente
JT8D
Administrator
Administrator
Messaggi: 16313
Iscritto il: 2 agosto 2005, 20:38
Località: Limbiate (MB)
Contatta:

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da JT8D » 14 agosto 2013, 19:21

Dichiarazione di Airbus sull'incidente:

http://www.md80.it/2013/08/14/le-dichia ... m-alabama/

Paolo
"La corsa di decollo è una metamorfosi, una quantità di metallo che si trasforma in aeroplano per mezzo dell'aria. Ogni corsa di decollo è la nascita di un aeroplano".


Avatar utente
JT8D
Administrator
Administrator
Messaggi: 16313
Iscritto il: 2 agosto 2005, 20:38
Località: Limbiate (MB)
Contatta:

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da JT8D » 15 agosto 2013, 11:27

"In their first press conference on Aug 14th 2013 the NTSB reported the A300-600F N155UP flight 5X-1354 crashed while on approach to runway 18 of Birmingham. There were three impact points prior to the final position of the wreckage over a distance of about 200 yards (200 meters). It appears the aircraft contacted a number of trees on the top of the hill prior to the first point of impact on the ground. The overwing section was extensively damaged by fire, the tail section was still smouldering preventing the black boxes to be recovered, the NTSB is optimistic to recover the boxes the next day. The investigation will "begin in earnest tomorrow morning". Initial information, subject to verification, suggests the crew did not issue a distress call.

Birmingham Shuttlesworth International Airport offers a Localizer Approach and a RNAV(GPS) Approach to runway 18, length 7,099 feet/2,160 meters."


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

Paolo
"La corsa di decollo è una metamorfosi, una quantità di metallo che si trasforma in aeroplano per mezzo dell'aria. Ogni corsa di decollo è la nascita di un aeroplano".


Avatar utente
sigmet
FL 500
FL 500
Messaggi: 6168
Iscritto il: 23 dicembre 2008, 12:08

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da sigmet » 15 agosto 2013, 19:41

Comincio a pensare di spedire i miei pacchetti via nave... :roll:
Ci sedemmo dalla parte del torto visto che tutti gli altri posti erano occupati.

Avatar utente
bigshot
10000 ft
10000 ft
Messaggi: 1116
Iscritto il: 19 dicembre 2011, 2:33
Località: VCE

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da bigshot » 15 agosto 2013, 19:48

FDR e CVR non sembrano messe benissimo dalle foto NTSB...


Avatar utente
AirGek
FL 500
FL 500
Messaggi: 12313
Iscritto il: 7 dicembre 2008, 12:02
Località: 12 o'clock opposite direction

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da AirGek » 15 agosto 2013, 19:56

E meno male che li fanno arancioni per facilitarne l'individuazione...
Football, basketball, baseball, tennis, golf? No thanks, I fly. Why? Because all that stuff requires one ball only!

Avatar utente
JT8D
Administrator
Administrator
Messaggi: 16313
Iscritto il: 2 agosto 2005, 20:38
Località: Limbiate (MB)
Contatta:

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da JT8D » 16 agosto 2013, 21:48

"In their second press conference on Aug 15th the NTSB reported the black boxes were recovered at about 11:00L after 3 hours of work, the boxes were blackened and sooted, the NTSB however is optimistic to retrieve good data from the boxes. The boxes are being shipped to Washington for analysis where they should arrive in the evening. It should be known on Friday (Aug 16th) whether there are good data on the boxes. Preliminary information shows no evidence of an engine's uncontained failure or fire prior to impact, there is also no evidence of a pre-impact ingestion of foreign objects. The radar data have been obtained. There are no indications of failure of runway/approach lighting, subject to verification. Runway 06/24 was closed at the time of the accident for maintenance of runway center line lights."

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

Paolo
"La corsa di decollo è una metamorfosi, una quantità di metallo che si trasforma in aeroplano per mezzo dell'aria. Ogni corsa di decollo è la nascita di un aeroplano".


Avatar utente
Talpo71
02000 ft
02000 ft
Messaggi: 204
Iscritto il: 20 agosto 2007, 15:28

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da Talpo71 » 20 agosto 2013, 10:23

Aggiornamenti da AvHerald:

In their third press briefing on Aug 16th 2013 the NTSB said, the "recorders did their job", there are good data, the cockpit voice recorder as well as the flight data recorder hold the entire flight. The captain (ATPL, 8,600 hours total, 3,200 hours on type) was pilot flying, the first officer (ATPL, 6,500 hours total, 400 hours on type) was pilot monitoring, the crew briefed the LOC approach runway 18, 2 minutes prior to the end of recording the aircraft received landing clearance on runway 18, 16 seconds before end of recordings there are two audible alerts by the GPWS "Sink Rate! Sink Rate!", 13 seconds prior to end of recording one crew member said "runway in sight", 9 seconds prior to end of recording sounds consistent with impact occurred. The flight data recorder contains more than 400 parameters requiring verification that these parameters are valid, this process takes time. It holds 70 hours of data including the entire accident flight. There were two controllers on duty at Birmingham tower, one controller was taking a break as permitted. The remaining controller observed the crash, he saw sparks and a large bright orange flash that he interpreted as breaking of a power line, he saw the landing lights, then no longer saw the landing lights and instead saw a large orange glow, he activated the crash button. There were no alerts regarding minimum safe altitude issued by his radar system. The crew started their "duty day" in Rockford,IL at 9:30pm on Aug 13th and flew to Peoria,IL as flight 5X-617 on A306 N161UP, then to Louisville,KY again as flight 5X-617 on N161UP before departing for the accident flight 5X-1354 on N155UP.

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.


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

Claudio


Avatar utente
JT8D
Administrator
Administrator
Messaggi: 16313
Iscritto il: 2 agosto 2005, 20:38
Località: Limbiate (MB)
Contatta:

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da JT8D » 20 febbraio 2014, 20:34

Oggi su AvHerald è stato riportato questo aggiornamento sull'evento: "On Feb 20th 2014 the NTSB released a number of documents into their public docket as part of the scheduled public hearing into the crash. The factual report submitted by the investigators states, that the aircraft performed a LOC 18 approach to Birmingham following an eventless flight with the crew, according to testimonies by ground personnel at Louisville in good/normal mood, intercepting the localizer at 2500 feet MSL. After crossing BASKN at 2500 feet the aircraft began the descent, the rate of descent increased to 1500 fpm and the aircraft descended through the decision altitude (1200 feet MSL, 556 feet AGL) at 1500 feet per minute rate of descent. An aural "sink rate" alert was raised by the EGPWS at 235 feet AGL (1536 fpm), 7 seconds after the sink rate the aircraft contacted tree tops and terrain about 1.2nm short of the runway threshold, portions of the aircraft came to rest about 0.75nm from the runway threshold. The captain (58, ATPL, 6,406 hours total, 3,265 hours on type) was pilot flying, the first officer (37, ATPL, 4,721 hours total, 403 hours on type) was pilot monitoring. The factual report also stated, that the charts used by the crew still showed the remark "When VGSI inop, procedure NA (not authorized) at night" that had been cancelled and revoked by the FAA in December 2011. The charts were only updated following the crash. The flight data recorder showed the aircraft was on autopilot maintaining 2500 feet while intercepting the localizer, the autopilot captured the localizer successfully and subsequently tracked the localizer until end of recording. A vertical speed of -700 fpm was selected into the master control panel, the aircraft began to descend below 2500 feet MSL consistent with intercepting the glidepath, 26 seconds after the begin of the descent the vertical rate was increased to 1500 fpm in the master control panel followed by the change of target altitude from 2500 feet to 3775 feet MSL. 45 seconds after the vertical speed was increased to -1500 fpm the EGPWS sounded "Sink Rate", an immediate response reduced the rate of descent to about -500 fpm. The control column position began to move towards nose up commands, 8 seconds after the EGPWS warning the autopilot disconnected (not stated whether disconnected by pilot command or automatically disconnected), an autopilot disconnect aural warning occurred, the autothrottle changed from speed to retard mode and the recording ended showing 7 degrees nose up and 138 KIAS at 14 feet AGL at last recording. The factual report regarding the cockpit voice recording shows the crew believed they were kept high and were complaining just after reading the final landing checklist and decided to use vertical speed. Shortly after the missed approach altitude was selected, both crew again commented they were too high for the approach, then the first officer commented "thousand feet", instruments cross checked, no flags, the captain remarked "DA is twelve hundred", then called 2 miles, shortly after the EGPWS sounded "Sink Rate", the captain got visual with the runway, the first officer confirmed runway in sight, the captain stated "autopilot's off", the autopilot cavalry charge (disconnect) sound was recorded following by first sounds of impact within a second after the begin of the cavalry charge, the EGPWS sounded "too low Terrain", the captain asked "Did I hit something?" followed by exclamations from both crew and sounds of impact until end of recording."

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

Paolo
"La corsa di decollo è una metamorfosi, una quantità di metallo che si trasforma in aeroplano per mezzo dell'aria. Ogni corsa di decollo è la nascita di un aeroplano".


Avatar utente
JT8D
Administrator
Administrator
Messaggi: 16313
Iscritto il: 2 agosto 2005, 20:38
Località: Limbiate (MB)
Contatta:

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da JT8D » 10 settembre 2014, 20:17

Ieri AvHerald ha riportato:

On Sep 9th 2014 the NTSB conducted their board meeting to determine the cause of the crash and concluded the probable causes of the crash were:

- the crew continued an unstabilized approach into Birmingham-Shuttlesworth International Airport in Birmingham, Ala.

- the crew failed to monitor the altitude and inadvertently descended below the minimum descent altitude when the runway was not yet in sight.

Contributing factors were:

- the flight crew's failure to properly configure the on-board flight management computer

- the first officer's failure to make required call-outs

- the captain's decision to change the approach strategy without communicating his change to the first officer

- flight crew fatigue

The NTSB stated the final report will become available in a number of weeks.


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

Paolo
"La corsa di decollo è una metamorfosi, una quantità di metallo che si trasforma in aeroplano per mezzo dell'aria. Ogni corsa di decollo è la nascita di un aeroplano".


Avatar utente
JT8D
Administrator
Administrator
Messaggi: 16313
Iscritto il: 2 agosto 2005, 20:38
Località: Limbiate (MB)
Contatta:

Re: Incidente Birmingham - AL - USA (thread tecnico)

Messaggio da JT8D » 2 giugno 2015, 11:50

E' stato rilasciato il Final Report su questo evento:

http://www.ntsb.gov/investigations/Acci ... AR1402.pdf

Un riassunto dei fatti salienti è riportato anche da AvHerald:

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

Paolo
"La corsa di decollo è una metamorfosi, una quantità di metallo che si trasforma in aeroplano per mezzo dell'aria. Ogni corsa di decollo è la nascita di un aeroplano".


Rispondi