|

|
UNCONTROLLED DESCENT AND COLLISION WITH TERRAIN
USAIR FLIGHT 427, BOEING 737-300, N513AU
Approach, Pittsburgh, PENNSYLVANIA
SEPTEMBER 8, 1994
Synopsis:
On September 8, 1994, about 1903:23
eastern daylight time, USAir (now US Airways) flight 427, a Boeing 737-3B7
(737-300), N513AU, crashed while maneuvering to land at Pittsburgh International
Airport, Pittsburgh, Pennsylvania. Flight 427 was operating under the
provisions of 14 Code of Federal Regulations Part 121 as a scheduled domestic
passenger flight from Chicago-O'Hare International Airport, Chicago, Illinois,
to Pittsburgh. The flight departed about 1810, with 2 pilots, 3 flight
attendants, and 127 passengers on board. The airplane entered an uncontrolled
descent and impacted terrain near Aliquippa, Pennsylvania, about 6 miles
northwest of the destination airport. All 132 people on board were killed,
and the airplane was destroyed by impact forces and fire. Visual meteorological
conditions prevailed for the flight, which operated on an instrument flight
rules flight plan.
The National Transportation Safety Board determines that the probable
cause of the USAir flight 427 accident was a loss of control of the airplane
resulting from the movement of the rudder surface to its blowdown limit.
The rudder surface most likely deflected in a direction opposite to that
commanded by the pilots as a result of a jam of the main rudder power
control unit servo valve secondary slide to the servo valve housing offset
from its neutral position and overtravel of the primary slide.
The safety issues in this report focused on Boeing 737 rudder malfunctions,
including rudder reversals; the adequacy of the 737 rudder system design;
unusual attitude training for air carrier pilots; and flight data recorder
(FDR) parameters.
Safety recommendations concerning these issues were addressed to the Federal
Aviation Administration (FAA). Also, as a result of this accident, the
Safety Board issued a total of 22 safety recommendations to the FAA on
October 18, 1996, and February 20, 1997, regarding operation of the 737
rudder system and unusual attitude recovery procedures. In addition, as
a result of this accident and the United Airlines flight 585 accident
(involving a 737-291) on March 3, 1991, the Safety Board issued three
recommendations (one of which was designated "urgent") to the
FAA on February 22, 1995, regarding the need to increase the number of
FDR parameters.
Commento all’indagine e note di collegamento
di Aldo C. Pezzopane
L’investigazione di questo
disastro aviatorio passerà alla storia dell’accident investigation
come una delle più complesse e approfondite che siano mai state
effettuate e segnerà il progresso di questa disciplina in modo
significativo, come è avvenuto per altri incidenti in passato nei
quali l’avaria meccanica e il fattore umano si sono intrecciati in un
groviglio apparentemente inestricabile di causalità ed effetti.
Gli incidenti dei Comet della fine degli anni ’50 furono le prime sfide
per questo tipo di analisi ma le tecniche e gli strumenti per l’investigazione
erano primordiali, poi avvennero, in periodo più recente, gli incidenti
dei DC10 a causa di un difetto alla chiusura dei portelloni cargo [il
disastro del DC10 THY in decollo da Orly fu il più grave], o il
disastro di Chicago del DC10 American Airlines conseguente ad un errato
assemblaggio del gruppo motore-pilone all’ala in fase di manutenzione,
oppure quello del B747 JAL che perse tutti i comandi idraulici perchè
furono danneggiate le tubazioni a causa del cedimento della paratia posteriore
della zona pressurizzata.
Anche il disastro del B747-100 della TWA esploso in volo dopo il decollo
da New York ha posto ardui interrogativi agli investigatori fino a quando
vennero ipotizzati problemi di isolamento elettrico in presenza di vapori
di carburante. Questi fattori sono riemersi anche in relazione all’esplosione
al suolo all’aeroporto di Bangkok di un B737 THAY avvenuta il 3 marzo
2001.
A nostro parere anche l’investigazione del disastro di Ustica con le conclusioni
di Frank A. Taylor del Cranfield Institute of Aeronautics ha marcato con
il peso del metodo scientifico l’evoluzione del processo investigativo.
[Taylor's
analysis of Ustica accident]
Il Final Report di
ben 370 pagine dell’NTSB sul disastro di Pittsburgh fu completato dopo
5 anni di analisi approfondite, di ipotesi e di verifiche, ed è
indicativo della enorme difficoltà di ricostruire un puzzle in
cui i fattori tecnici, ambientali e umani non consentivano un orientamento
netto verso le vere cause della tragedia. Data la complessità del
rapporto esso non può essere affrontato come se si leggesse un
resoconto o un elencazione di eventi, quindi non è proponibile
se non a specialisti della materia i quali, da uno studio attento, possono
trarre da questa esperienza investigativa ulteriori insegnamenti.
Quello che caratterizzò le difficoltà dell’investigazione
del disastro di Pittsburgh fu innanzitutto la mancanza della registrazione
di dati importanti a causa del tipo di FDR [non c’erano i dati relativi
alla posizione dei comandi di volo]. L’analisi del profilo di volo degli
istanti che precedettero l’impatto non aveva alcuna possibile spiegazione
se non quella di un grossolano errore di manovra per la rimessa da turbolenza
di scia. Ma questa ipotesi non si accordava con il comportamento dei piloti,
con il loro record di proficiency, con quello che fu ascoltato dalla registrazione
delle loro voci e delle comunicazioni.
Inoltre questo accident si sommava ad un lungo elenco di incidenti di
diversa gravità nei quali era evidente un malfunzionamento od una
risposta anomala del timone o degli alettoni o di entrambi i comandi.
Nel rapporto finale sul disastro di Pittsburgh, vengono citati un centinaio
di questi rudder-related events, alcuni conclusi con esito disastroso
[fuori degli USA] e definiti a suo tempo CFIT [Controlled Flight Into
Terrain]. La denominazione CFIT andrebbe, ovviamente, rivista in quanto
quegli aeromobili non potevano essere considerati "controllable".
Uno dei primi avvenne ad un B737-200 [United Airlines 585] in avvicinamento
a Colorado Spring [3 marzo 1991]. Le evidenze del Flight Data Recorder
e del Cockpit Voice Recorder fecero sospettare un upset dovuto a forte
turbolenza in aria chiara ma esso non avrebbe potuto far impattare al
suolo l’aeromobile se non vi fossero state azioni apparentemente scoordinate
sui comandi. La distruzione completa dell’aeromobile dovuta all’impatto
e all’incendio [postcrash-fire] non permise di esaminare i componenti
dei servocomandi, in particolare il Rudder Power Control Unit [PCU], un
selettore idraulico costituito da due pistoncini coassiali dotati di fori
di collegamento alla mandata e al ritorno di pressione da un singolo impianto
idraulico. Altri incidenti in cui l’aeromobile andò distrutto comportarono
la stessa difficoltà di esaminare questo componente. Analogamente
avvenne per il PCU del B737 USAir.
La descrizione della struttura del PCU e del suo funzionamento in dettaglio
prende diverse pagine del rapporto ed è indicativa del meticoloso
lavoro di indagine, svolto tramite numerosissimi test su PCU con diverso
tempo di utilizzazione in tutte le condizioni di impiego dell’impianto.
In sostanza, il grippaggio dei pistoni scorrevoli a causa di surriscaldamento
del fluido idraulico [e/o in concomitanza con esso] avrebbe provocato
una selezione della pressione all’impianto che azionò la superficie
del timone nella direzione opposta a quella comandata dalla pedaliera.
[Va ricordato che la conclusione è sempre una proposizione in termini
probabilistici]
Non ritengo valga qui la pena di approfondire la descrizione di questa
dinamica mentre ritengo molto interessante proporre le valutazioni che
hanno condotto a identificare il comportamento, le reazioni stupite, poi
presumibilmente disperate, dei piloti di fronte al fatto che una normale
azione sulla pedaliera facesse deviare la stessa "inesorabilmente"
a fondo corsa dalla parte opposta, con l’aeromobile che rispondeva
inclinandosi da quella parte come un animale impazzito.
Dal Final Report ripreniamo il capitolo che riguarda le prove fatte a
terra per rilevare le sensazioni provocate dalla inversione del comando
del timone.
Queste impressioni soggettive sono state messe in relazione con la ricostruzione
delle sensazioni dei piloti del B737 USAir, rese possibili dall’analisi
delle voci e dei rumori, e hanno permesso di definire con elevata probabilità
come si siano svolti gli eventi.
1.16.5.4.9 Ground Demonstration of Rudder PCU Servo Valve Jam
In June 1997, the Safety Board participated in a ground demonstration
conducted by Boeing at its facility in Seattle, Washington. The demonstration
was intended to identify and document the cockpit characteristics of a
rudder PCU servo valve secondary slide jam. The demonstration was accomplished
in a newly manufactured 737-300 airplane that was fitted with a special
tool to simulate a rudder PCU servo valve secondary slide jam at three
different positions (about 0 percent, about 25 percent, and about 50 percent
of travel from the neutral position). The demonstration was conducted
while the airplane was parked on the ground with both engines off and
with hydraulic systems powered by an external source of power.
Before the demonstration began, the participants sat in the pilot seats
of another newly manufactured 737-300 and manipulated the rudder pedals
to become familiar with the feel of a normally functioning 737 rudder
system on the ground. The participants then moved to the airplane that
was fitted with the special jamming tool, and each participant manipulated
the rudder pedals under the three simulated rudder jam conditions. As
recorded in the Human Performance Group Chairman’s addendum report, one
Safety Board participant described the demonstration as follows:
All demonstrations were conducted in the cockpit, with Boeing test pilot…sitting
in one of the pilot seats to coordinate the procedure…. When I was the
active participant, I sat in the right seat wearing the seat belt.The
first demonstration in the test airplane represented a jam of the secondary
slide about 25 percent off [its] neutral position. I pushed the respective
rudder pedals slowly to their full down positions as though I were performing
a slow rudder system check. The right rudder pedal seemed easier to push
down than the left pedal, although the difference seemed subtle. I then
performed about 7 tests in which I [applied] hard left rudder. With one
or two exceptions, this input triggered a rudder reversal on the pedals.
Immediately after my input, the left rudder pedal began moving outwards
until it reached the upper stop. The motion was slightly slower than an
input I would expect from a human. The motion was steady and continued
without pause no matter how hard I pushed to counter it ("unrelenting"
was a description that, at the time, seemed to capture my impression)….
[When] I…"stopped fighting" the motion, [the] action of the
rudder system ended almost immediately and the rudder pedals returned
to the neutral position. On subsequent trials, I "stopped fighting"
the rudder motion earlier, before the left pedal had reached the upper
stop. Again, the rudder motion stopped almost immediately as soon as I
stopped applying pressure, no matter where the pedal was located, and
the pedals returned to neutral.
The second demonstration represented a jam of the secondary slide about
0 percent off [its] neutral position. I pushed each respective rudder
pedal slowly to the lower stop as though performing a rudder system check.
The right pedal again seemed easier to push than the left pedal, although
the difference was small. I also pushed the rudder pedals aggressively
and abruptly, but this did not produce a rudder reversal situation.
The third demonstration represented a jam of the secondary slide about
50 percent off [its] neutral position. I performed about 9 trials. WhenI
moved the pedals slowly and steadily [as though performing a rudder system
check], I was generally able to move the pedals to their stops without
starting a reversal. Sometimes, however, even a slow input initiated a
rudder reversal situation (this time with the right pedal moving to the
upper stop). Any abrupt motion on the pedals initiated an immediate rudder
reversal situation. The rudder reversal motion was faster than was the
case with a jam in [the] 25 percent position, perhaps similar to a relaxed
or slow input speed by a human operator. Again, it was impossible to stop
the motion by physically pushing against the rudder pedal. On several
trials, I tried relaxing my input momentarily before the rudder pedal
reached the upper stop. I found that the rudder reversal motion continued.
This [was not true in the jam at the approximate 25 percent position],
when the relaxation of pressure seemed to automatically stop the reversal
motion. This motion was faster, easier to initiate, and more difficult
to stop. Other participants reported similar experiences during the demonstrations.
They described the rudder back pressure during the reversal as "machine-like,"
"startling," and "relentless."
Dopo aver letto e riflettuto sulle sensazioni di qualcuno che, seduto
al posto di pilotaggio con l’aeromobile fermo al suolo, sta eseguendo
delle prove in tutta tranquillità e con tutto il tempo a disposizione,
riflettete ora sull’effetto che hanno avuto le condizioni sui piloti ai
comandi di un aeromobile in avvicinamento e capirete anche l’importanza
di quello che viene indicato come "speech analysis".
Avete i piedi sulla pedaliera e ad una rapida, breve, pressione del piede
sul pedale [ad esempio il sinistro] per uno spostamento di un paio di
pollici al massimo, sentite che il pedale reagisce contro il vostro piede
spingendo decisamente contro di esso, e, nonostante facciate sforzi immani
per contrastarlo, arriva a fondo corsa. Contemporaneamente l’aeromobile
si inclina violentemente verso destra, gli alettoni non hanno efficacia
e l’azione istintiva sul timone per la rimessa in linea di volo è
ancora quella di spingere con il piede sinistro.
Quale scintilla di creatività avrebbe potuto ispirare i piloti
a compiere l’azione anti-isintiva di spingere proprio sul pedale lontano?
La risposta a fra poco nella conclusione (stay with us).
Human Performance Investigation of the Flight 427 Accident
By Malcolm Brenner, National Transportation Safety Board
About 7:03 P.M., September 8, 1994, USAir (now US
Airways) Flight 427, a Boeing 737-300 airplane, crashed
while maneuvering to land at Pittsburgh International Airport.
All 132 persons onboard were killed.
The accident led to the longest and one of the most difficult investigations
in the history of the National Transportation Safety Board (NTSB),
an independent agency of the United States government tasked with investigating
major transportation accidents and making recommendations to prevent their
recurrence. To reach its determination on the cause of the accident, issued
at its public board meeting on March 24, 1999, the Safety Board drew heavily
on a human performance effort that tried, by a variety of investigative
approaches, to explain the pilots' actions during the most critical
moments of the flight.
Human performance is routinely part of every major investigation conducted
by the Safety Board. A human performance investigator launched with the
team that responded to the accident, and a human performance group was
formed at the site that collected medical, professional, and personal
evidence on the pilots. All evidence appeared routine.
The flight data recorder (FDR) on Flight 427 was unusually limited. It
recorded only 11 parameters, providing no data for such major variables
as aileron and rudder position. However, analysis of the FDR information
indicated that a rudder motion could underlie the accident sequence. The
motion of the airplane was smooth until, about 5,000 feet above the ground,
the airplane encountered turbulence due to the wake of another airplane
and entered a left roll from which it never recovered. The wake turbulence
itself would not have been sufficient to cause the accident, as confirmed
by flight testing, but a full left rudder motion beginning shortly after
the wake encounter and maintained until impact (or near impact) would
recreate the motion of the accident airplane. Engineering analysis indicated
that only a full rudder motion, of all control surface combinations,
would recreate the accident profile, while investigative evidence discounted
alternative explanations such as midair collision, bird strike, or structural
damage.
Based on this evidence, the investigation began to center on rudder issues.
The Systems Group attempted to identify hardware failures that might lead
to a full rudder input, while the Human Performance Group attempted to
collect available human evidence to judge whether the pilots might have
input full rudder inappropriately following a wake turbulence penetration.
Beginning about one year after the accident, an expanded Human Performance
group began an enlarged investigation during which the group:
• Reviewed in detail the accident pilots' flying and medical histories.
• Reviewed and analyzed wreckage information on seat position and rudder
pedal damage for suggestions of control use at the moment of impact.
• Conducted ergonomic studies of leg force application on the B-737 rudder
pedal, including issues involved in crew physical dimensions and B-737
anthropometric seat design limits.
• Conducted speech analysis on the audio recording of the cockpit voice
recorder (CVR) in an attempt to extract additional information on crew
actions.
• Recreated and analyzed the motions, visual cues, and auditory cues of
the last minute of the accident flight, using large motion simulators
at NASA and Boeing, by pairing the FDR-recorded motions with the CVR-recorded
sounds.
• Analyzed the air traffic control view of the accident situation recreated
by the FAA's Systematic Air Traffic Operations Research Initiative (SATORI).
• Reviewed evidence of pilot responses to wake turbulence and other upsets
in available accident/incident records as well as interviews conducted
by the group.
• Obtained from NASA's Aviation Safety Reporting System (ASRS) a structured
callback project on in-flight upsets, involving a detailed interviewing
of all airlines pilots who reported a multi-engine, turbojet upset between
May-October 1995 [in addition to reviewing evidence from an ongoing ASRS
callback project on wake turbulence penetrations].
• Reviewed evidence from the quick access recorder (QAR) project conducted
as part of the investigation, involving in-flight rudder usage during
about 57,000 hours of revenue passenger service by Boeing 737 pilots on
a European airline between May 1996 to June 1997.
Many of these approaches were unusual for an investigation. For example,
the pairing of FDR and CVR information in a large motion simulator was
novel. The Vertical Motion Simulator (VMS) at NASA-Ames Research Center,
which was used in one of these efforts, is the world's largest motion
simulator (with 60 feet of vertical travel). NASA and Safety Board staff
cooperated to develop a simulation that accurately represented the flight
dynamics, accelerations, and visual cues of the final minute of the accident
flight. By approval of the Board members, the appropriate segment of the
CVR audio recording was allowed to be played outside of the Safety Board
facilities for the first time so that it could be paired with this motion
simulation. The members of the Human Performance Group experienced the
resulting simulation numerous times, riding in the simulator cab with
motion/speech cues only, with motion/speech/visual cues, and with sections
of the simulation emphasized, in an effort to understand the cues experienced
by the accident pilots that were reflected in their responses. In support
of the human performance effort, an expert in human spatial orientation
experienced this motion simulation and advised that disorientation of
the accident pilots was unlikely (due, especially, to the clear visual
conditions present at the time of the accident). In addition, three members
of the Safety Board experienced this simulation as part of their effort
to better understand the accident and determine a probable cause.
Another initiative of the human performance investigation was to conduct
an extensive review of available accident/incident information to identify
the action of pilots involved in upset situations that resembled those
of the accident. For example, as a result of this review and a search
of the FAA's Pilot Incapacitation database, the Human Performance Group
identified two airline incidents in which pilots in revenue passenger
service were confronted without warning with a full rudder deflection.
Both cases involved Boeing 737 airplanes on final approach to landing
One airplane was below 600 feet in gusty conditions, while the other
was at 1,500 feet in instrument conditions. In both cases, the rudder
moved to full deflection as the result of the sudden medical incapacitation
of the flying pilot with the pilot's leg becoming rigid on the rudder
pedal. The Human Performance Group was interested in the responses of
the nonflying pilots who, although startled, took control of the airplane
in both cases and affected a safe missed approach and subsequent landing.
One of the most important sources of evidence proved to be speech analysis
on the CVR recording. The CVR provided audio recordings of the last 30
minutes of the accident flight captured both from an overhead cockpit
microphone and from individual boom microphones worn by the crewmembers.
Recording quality was excellent and allowed speech analysis. Speech was
clearly understood, breathing was often audible, and computer analysis
could be made of acoustic aspects of speech including fundamental frequency
("pitch"), amplitude ("loudness"), and speaking rate. In addition to making
laboratory measurements, the Safety Board enlisted the help of three outside
experts' to provide written observations on different aspects of speech
for use by the Human Performance Group in evaluating the CVR information.
Speech analysis provided clear insights on the crew responses. Prior
to the wake turbulence encounter, cockpit communications were routine.
The captain responded to the turbulence with an immediate exclamation
("sheeze"), followed, during the 25 second upset period before impact,
by comments related to the ongoing problems ("hang on," "what the hell
is this?"). Shortly before impact, the captain made a transmission to
Air Traffic Control advising that the airplane was experiencing an emergency.
Speech analysis indicated that the captain's respiration rate increased
over the course of the upset period. Fundamental frequency and amplitude
measures showed a similar increase. Yet the fact that the captain made
an emergency transmission, and level of his speech characteristics during
the transmission, suggested that the captain had not reached panic levels
at this time. Rather, there was an impression of a pilot trying to deal
with a problem and showing increased psychological stress as his efforts
were unsuccessful.
In the case of the first officer, who was the flying pilot, speech analysis
highlighted an important observation. The first officer was talking at
the time of the wake penetration, but interrupted his speech and said
little other than emotional exclamations during the upset period. However,
he emitted short grunting sounds during the first seconds of the upset.
Normal use of the cockpit controls should not produce these types of straining
sounds. No similar sounds were recorded from the captain during this period.
The importance of the human evidence became clear as the investigation
advanced and uncovered a possible new failure mechanism in the rudder
system. By 1997, the Systems Group determined that, under very rare circumstances,
a jam in the rudder power control unit (PCU) servo valve could cause a
rudder reversal problem in which the rudder moved in the direction opposite
to that commanded by the pilot. A human performance investigator, participating
in a demonstration prepared by Boeing, found that a pilot would have difficulty
understanding or stopping this reversal. The pilot, pushing down on the
pedal to make a small input, would find that the pedal was unusually stiff
or that the pedal might start to rise in a direction opposite to the input.
Pushing harder would not help. A pilot would not be strong enough to overpower
the hydraulic system and, as long as the pilot maintained pressure on
the pedal, the rudder itself would move fully over in the opposite direction
to that being commanded.
This rudder reversal provided a specific scenario
that accounts for the human evidence of the Flight 427 accident. It would
explain the entry of a full rudder motion, as a pilot attempting to make
a small rudder input in response to turbulence would inadvertently cause
the rudder to move fully in the opposite direction. It would explain the
confusion shown by the crew in trying to understand and recover from the
situation.
The crew's confusion
under this scenario would be increased significantly by the fact that
Flight 427 was below the crossover point of aileron-rudder authority at
the time the upset began. This is a narrow range of airspeeds and flap
settings in which the ailerons provide less roll authority than the rudder.
Under a rudder reversal scenario, the 427 pilots would have found that
rudder pedal was not responding properly and then that the wheel did not
have enough authority to roll the airplane back to a level attitude.
Finally, it would explain the grunting sounds
of the first officer. Engineering analysis determined that the rudder
pedal would have begun reversing at the same time the first officer grunted,
a plausible reaction of a pilot fighting a rudder pedal that refused to
respond to his input. No other explanation of the grunting could be determined
from other likely control inputs.
By contrast, the human performance evidence did not support an explanation
of the accident based only on pilot input. To cause the accident, a pilot
would have to input full left rudder early in the upset period, hold this
input for at least 10 seconds as the airplane lost control, and the second
pilot would have to allow this wrong input to be maintained. The human
performance investigation could provide no plausible explanation under
which this might have happened.
Airline pilots routinely recover from wake turbulence encounters, even
those described as "startling" and extreme, and often from altitudes lower
than that of Flight 427 (according to ASRS records). No airline accidents
in the United States have been caused by wake turbulence encounters from
the altitude of Flight 427 (according to NTSB records). Although pilots
have entered inappropriate rudder inputs during emergency upset situations,
no instance could be found in which a pilot held a wrong rudder input
when it caused the airplane to go visibly out of control (according to
a review of worldwide accident/incident records). No instances were found
in which pilots entered a full rudder input for any reason during Boeing
737 revenue flights (according to the QAR project). No instances were
found in which a pilot, confronted by a surprise full rudder input, failed
to take appropriate corrective action. On balance, the human performance
evidence could not explain why a pilot would make a full rudder input,
why the pilot would hold this wrong input as the airplane went out of
control, and why the second pilot would allow this to happen.
As part of the Flight 427 investigation, the NTSB examined a previous
Boeing 737 accident at Colorado Springs, on March 3, 1991, involving United
Airlines Flight 585. It also examined a Boeing 737 incident at Richmond,
Virginia, on June 9, 1996, involving Eastwind Airlines Flight 517. In
both cases, the human evidence (including self-report of the surviving
pilots) was found to be consistent with a rudder reversal scenario.
The Safely Board determined that the probable cause of the USAir 427
accident was "a loss of control of the airplane resulting from the
movement of the rudder surface to its blowdown limit. The rudder surface
most likely deflected in a direction opposite to that commanded by the
pilots as a result of a jam of the main rudder power control unit servo
valve secondary slide to the servo valve housing offset from its neutral
position and overtravel of the primary slide."
Beginning in 1998, Boeing began
replacing the rudder PCU units on all Boeing 737 airplanes with a new
unit designed to prevent a rudder reversal possibility.
In reaching its determination, the Safety Board drew on an active human
performance investigation.
The final report on this accident is now available
from the NTSB web page at: http://www.ntsb.gov/Publictn/1999/AAR9901.htm
Nota conclusiva
Rispondiamo alla domanda di poc’anzi.
Nessun intuito o creatività avrebbe potuto far scattare un comportamento
anti-istintivo se non un’esperienza di qualcosa di analogo [ma
è sufficiente il ricordo di un racconto].
Con il senno di poi è possibile argomentare che se i piloti avessero
sentito parlare anche una sola volta di inversione di comandi, magari
in relazione ad un grave incidente, forse il fatto avrebbe sedimentato
in qualche angolo della memoria per scattare, stimolato da un disperato
istinto di conservazione, a far rilasciare quella inutile pressione su
un pedale e ad agire in modo opposto.
Forse in tal modo i piloti avrebbero avuto il tempo di sintonizzarsi
su tale comportamento anomalo ed anti-istintivo del timone e forse
avrebbero portato l’aereo e i suoi occupanti salvi in pista. Questi «forse»
valgono la necessità di far sapere ai piloti le dinamiche degli
incidenti per predisporre un’intuizione che può salvare molte vite
umane.
E’ il caso qui di ricordare quanto avvenne ad un DC10 United Airlines
[crash-landed] a Sioux City. I piloti riuscirono ad arrivare in pista
nonostante avessero i comandi in avaria, utilizzando la spinta differenziata
di due soli motori efficienti. Ma avevano tempo a disposizione.
Anche i piloti del B747 JAL ricordato all’inizio [perdita dei comandi
di coda] erano riusciti a comprendere come arrestare l’oscillazione fugoide
agendo sui motori e sull’uso differenziato degli outboard e degli inboard
trailing edge flap. Queste sezioni mobili dell’ala provocano momenti a
picchiare o a cabrare a seconda dell’asimmetria di estensione. Purtroppo
erano nella zona motagnosa e non riuscirono a evitare gli ostacoli e contemporaneamente
a mantenere una parvenza di volo stabilizzato. Nell’impatto perirono 520
persone.
Per esperienza personale, verificata con quella dei colleghi che hanno
avuto sempre l’abitudine di mantenersi informati sulle esperienze degli
altri, posso affermare che ho evitato a volte situazioni critiche avendo
valutato il deteriorarsi delle condizioni operative sulla base del ricordo
di condizioni analoghe apprese da relazioni di incidenti. Si è
trattato quasi sempre di aspetti legati alle condizioni meteo o al traffico
aereo, più raramente legate ad avarie di impianti dell’aereo o
dei motori.
ll Gen. Chuck Yaeger, asso dell'USAF, nel suo famoso libro "The right
stuff" che è una autocelebrazione continua, sottolinea come ogni
situazione critica sperimentata nei voli operativi sui cieli d'Europa,
nella Seconda Guerra, ed in tempo di pace, nei voli di collaudo, sia stata
da lui superata grazie ad una dettagliatissima conoscenza della macchina
e dell'ambiente di volo acquisita con una preparazione scrupolosa ed una
pianificazione altrettanto meticolosa. Aggiunge però, che spesso
era stato il ricordo di esperienze vissute da altri e fissate nella memoria,
a far scattare il comportamento migliore per portare la pelle a casa.
In guerra Chuck Yaeger volò con il North American P-51 [meglio
noto come Mustang] e nel suo libro ne parla diffusamente elogiandone alcune
caratteristiche ed evidenziandone alcuni problemi. Ma senza andare a scomodare
l'asso statunitense disponiamo dell'esperienza di Renzo Dentesano che,
commentando questo articolo che state leggendo, mi ha raccontato come
la conoscenza dei problemi incontrati dagli altri può veramente
consentire di "portare la pelle a casa". L'evento risale a quando egli
era sottotenente in Aeronautica Militare [half century ago, you know?]
«Eravamo in volo di addestramento, in formazione di due, con quei vecchi
ma "poderosi" P-51D ereditati dal piano Marshall. Ero passato in posizione
di gregario e stavamo effettuando una serie di virate sfocate quando da
una di queste virate non mi fu possibile raddrizzare l'aeromobile e solo
una pronta riduzione di manetta mi impedì di troncare la coda del
leader.
Per quanti sforzi facessi sui comandi questi risultavano bloccati. Fortunatamente
eravamo in quota e decisi di ritardare il lancio. All'inizio avevo pensato
immediatamente ad una vite piatta, poi la sensazione di blocco dei comandi
mi portò a fare svariati e vani sforzi in ogni direzione. Ripensai
alla vite piatta e ricordai che qualcuno raccontava di esserne venuto
fuori estendendo il carrello. Immediatamente azionai la leva ed il carrello
venne fuori rumorosamente frenando e stabilizzando l'aeroplano. Una volta
a terra non fu possibile determinare che cosa era accaduto ma furono eliminati
tutti i posibili attriti lungo i cavi dei comandi. So per certo che fu
l'estensione del carrello ad eliminare la causa che mi aveva messo in
quella condizione, meccanica o aerodinamica che fosse e compresi allora
l'importanza di sapere e ricordare l'esperienza degli altri»
"You will not live long enough to make all possible errors, so
you must learn from the experience of others."
Questo è il
solo, vero, motivo per cui proponiamo queste riflessioni a coloro che
sono in prima linea.
Ulteriore riflessione sul surriscaldamento degli impianti idraulici
Il Caravelle SE-210, il primo jet francese di linea, era caratterizzato
da una proliferazione di impianti idraulici che servivano tutti i comandi
di volo, flaps, aerofreni e carrello-freni ruote compresi. Le funzioni
e le ridondanze di questi quattro impianti denominati con dei colori [blu,
verde, rosso, giallo] erano molteplici, erano un incubo nello studio della
macchina e richiedevano grande attenzione nell’impiego normale. Il malfunzionamento
di uno di essi, in particolare il blu e il verde, che azionavano i comandi
di volo [in caso di avaria di uno dei due subentrava il giallo], era condizione
di emergenza anche perché non c’era possibilità di collegamento
meccanico tra volantino-pedaliera e superfici di comando. Stiamo parlando
di un disegno di circa 40 anni fa eppure non si conoscono incidenti significativi
dovuti a grippaggio/surriscaldamento di componenti idraulici su questo
aeromobile.
Si deve aggiungere che i piloti erano addestrati ad operare cautelativamente
gli utilizzatori idraulici per evitare, appunto, surriscaldamenti del
fluido e dei componenti.
(acp)
|