Forty years after USAir Flight 499 overran a snowy runway in Erie, Pennsylvania, we look at how tailwind, pace, and snow mixed to slender the margins.
On the morning of 21 February 1986, USAir Flight 499 was approaching Erie Worldwide Airport (ERI) in Pennsylvania’s northwestern nook in instrument circumstances that left little room for error. Snow was falling. The ceiling hovered at 200 toes. Visibility was 0.5 miles. Braking motion had been reported truthful to poor.
Inside seconds of landing, the McDonnell Douglas DC-9-31 would slide off the tip of runway 24, overrun a runway finish mild, break by means of a fence, and are available to relaxation on a busy highway 180 toes past the pavement, narrowly lacking a number of automobiles on their Friday morning commute.
There have been 23 folks on board. One passenger sustained a minor head damage. There have been no fatalities. However the accident turned a transparent case examine in winter efficiency margins and operational determination making.
The Airplane and the Mission
The plane was DC-9-31 (reg. N961VJ), MSN 47506, delivered to Allegheny Airways (USAir’s predecessor) in 1970 and powered by Pratt & Whitney JT8D-7B engines. By February 1986, it had gathered greater than 42,000 airframe hours.
Flight 499 was working that morning on a routine flight from Toronto Pearson Worldwide Airport (YYZ) to what was then Better Pittsburgh Worldwide Airport (PIT), with an intermediate cease in Erie. The captain had roughly 8,900 whole flight hours, together with 5,900 within the DC-9. The primary officer (FO) had logged 4,880 hours whole, 2,420 in kind. Each have been present and correctly certified.
The accident occurred at roughly 0858 native time throughout touchdown.
A Runway Slowly Deteriorating
Climate that morning was marginal from the outset. A particular statement issued at 0650 reported a 300-foot overcast ceiling, 1.5 miles visibility in mild snow and fog, temperature and dewpoint each at freezing, and wind 030º at 10 knots.
Extra important than the ceiling was the runway situation. Runway 06/24 had been plowed, however just one snowplow was operational that morning. The operator acknowledged it sometimes left roughly one-quarter inch of snow behind. At 0715, braking motion was checked with a decelerometer, which indicated truthful to poor circumstances.
The crew, who dutied in in Toronto round 0700, mentioned the climate circumstances. Based on the NTSB report, the captain acknowledged that the climate in Erie was “not too good.” They decided that the gas load was enough to carry if crucial and proceeded with the brief 23-minute flight throughout Lake Erie as deliberate. Flight 499 pushed again from the gate at YYZ at 0756, 28 minutes delayed.
A Beechcraft King Air that landed round 0745 reported braking motion as poor and estimated one to 2 inches of moist snow on the runway, with no naked spots seen. When that plane departed round 0815, the pilot nonetheless noticed no uncovered pavement and estimated roughly one-half inch of snow even on plowed sections.
Plowing was halted at 0820 in anticipation of Flight 499’s arrival. No sand or chemical therapy was utilized. Gentle to average snow continued falling and intensified shortly earlier than touchdown. No additional plowing occurred for almost 40 minutes.
By the point the DC-9 arrived on closing, the runway was solely snow-covered.
Runway 06 Out of Attain
The crew initially deliberate an ILS strategy to runway 06. Nonetheless, runway visible vary (RVR) was reported at 2,800 toes, effectively under the required 4,000-foot minimal.
The captain elected to carry at 10,000 toes. Dispatch suggested that if runway 06 minimums couldn’t be met and touchdown on runway 24 with a tailwind was not licensed, the flight ought to proceed to Pittsburgh.
Runway 24 required one-half mile visibility and was not geared up with RVR sensors. Reported visibility matched that minimal. On the suggestion of USAir’s Erie Ops, the crew requested an ILS strategy to runway 24.
Initially, they believed winds have been 330 at 9, successfully a crosswind close to their allowable restrict beneath decreased visibility circumstances. However up to date wind studies informed a distinct story.
ERI Tower suggested winds 010 at 10 knots. Moments later, winds elevated to fifteen knots and have become variable between 010 and 020. On runway 24, these winds produced a ten to 11 knot quartering tailwind part.
USAir’s DC-9 Pilots’ Handbook and Jeppesen advisory pages have been specific: tailwind elements weren’t licensed for turbojet plane on runway 24 when the runway was moist or slippery. ERI’s runway 24, at simply 6,500 toes, was one in all 5 within the system with that restriction.
The crew obtained a number of wind studies indicating a tailwind part.
On brief closing, the FO tried to reference the crosswind and tailwind part chart. The captain instructed him to place it away and give attention to altitude callouts.
The airplane continued inbound.
Quick, Lengthy, and Dedicated
Flight information recorder (FDR) information confirmed the DC-9 maintained 130 to 135 knots on closing strategy, roughly 13 to 18 knots above Vref, which was 117 knots for that touchdown weight.
The plane descended to the 200-foot determination peak and remained there for roughly eight seconds earlier than persevering with the descent.
At strategy pace, eight seconds is critical. The plane would have traveled effectively over 1,500 toes horizontally whereas holding altitude. In snow-obscured circumstances with decreased runway definition, that ahead motion shifts the eventual landing level.
The FO later said that he noticed the bottom roughly 100 toes above determination peak. At roughly 50 toes above minimums, he may see the strategy lights and runway lighting however couldn’t clearly outline the runway floor itself as a result of it was fully snow-covered.
Visible cues have been current, however degraded.
As soon as descent resumed, landing occurred lengthy.
FDR evaluation positioned fundamental gear contact roughly 1,745 toes past the displaced threshold. Eyewitness measurements steered as a lot as 2,130 toes past. In both case, roughly 4,000 to 4,250 toes of the 6,500-foot runway remained.
Each pilots described the landing as agency. Spoilers have been armed however didn’t auto-deploy. On a slick, snow-covered floor, inadequate wheel spin-up seemingly prevented activation.
There was a seven-second delay earlier than the nostril gear contacted the runway. Throughout that interval, the plane traveled an extra 1,200 to 1,400 toes.
The captain manually deployed the spoilers, lowered the nostril, chosen reverse thrust, and utilized braking. He later reported that reverse thrust slowed the plane, however braking was not efficient.
The DC-9 drifted left and exited the runway floor at roughly 44 knots. It ran over a runway finish identifier mild, struck a chain-link fence, descended a 20-foot embankment, and got here to relaxation straddling a highway 180 toes past the runway finish.
Evacuation was textbook: Flight attendants deployed the ahead slide, ushering passengers off the plane. The crew secured the cockpit, checked for leaks (none), and notified the tower. The DC-9 was considerably broken and later written off.
The Arithmetic of Stopping
Douglas Plane and NTSB evaluation decided that roughly 4,087 toes of stopping distance have been required from the purpose of fundamental gear landing beneath the prevailing configuration, tailwind, extra pace, and runway situation. That determine included the seven-second delay earlier than nostril reducing.
Had the nostril been lowered instantly, permitting spoilers to deploy upon nostril gear compression and reverse thrust to be utilized directly, stopping distance may have been decreased to roughly 2,750 toes.
Even so, firm coverage explicitly prohibited touchdown on runway 24 with any tailwind part when the runway was moist or slippery.
In the long run, the NTSB concluded that the crash of Flight 499 was not the results of one mistake. It was a cascade.
The tailwind restriction was ignored. The strategy was flown quick. The plane floated at determination peak. Landing got here lengthy. Deceleration was not optimum.
The DC-9 handbook had addressed almost each a kind of variables. It warned that the primary 2,000 toes on a slush-covered runway are essentially the most essential as a result of hydroplaning reduces braking effectiveness. It emphasised monitoring spoilers on slippery surfaces, since computerized deployment relies on wheel spin-up or nostril gear compression. It outlined strict limitations for moist snow operations.
The crew had the data. However climate, shifting winds, and short-final workload blurred the strains between process and execution.
The dispatcher, counting on the wind data relayed by the crew, deferred to their on-scene judgment, as firm protocols require. Air site visitors management offered all out there climate updates. Nav aids checked out post-accident. No mechanical discrepancies have been discovered.
What remained was efficiency math.
A Private Footnote, Forty Years Later
I used to be seven years outdated when Flight 499 slid off the tip of runway 24. It occurred simply three miles from my childhood residence. As a child already obsessive about aviation, I keep in mind watching the protection and following each element of the cleanup and investigation. My dad drove me to the accident web site a number of occasions, and we have been there when the DC-9 was lifted from the roadway by crane.
Lower than a month earlier, the Area Shuttle Challenger catastrophe had shaken the nation and dominated headlines internationally. That occasion introduced nationwide grief. Flight 499 barely registered within the nationwide headlines of the day. Exterior of Erie, few folks seemingly keep in mind it. Nobody was killed. Just one passenger was injured.
However regionally, it was unforgettable. For a younger boy already fixated on aviation, it turned a kind of early recollections that quietly and completely imprints itself.
Wanting again 4 many years later, it’s onerous to not see how that snowy winter morning deepened my fascination with aviation. Not due to spectacle, however due to the self-discipline behind it. Efficiency charts. Tailwind limitations. Runway contamination. The unforgiving math of stopping distance.
Fortunately, Flight 499 didn’t finish in tragedy.
However on a snowy morning in Erie, the teachings discovered from USAir Flight 499 reinforce the onerous fact that in aviation, margins are by no means summary. And in winter circumstances particularly, each inch and each knot counts.
