Close

Electrical, Avionics & Air Data

Twenty Days Without Covers — The Blocked Pitot of Puerto Plata

Concept visualization for Twenty Days Without Covers — The Blocked Pitot of Puerto Plata

The 757 sat on a Caribbean ramp for twenty days with its pitot tubes open to the sky, then flew. The captain's airspeed indicator was dead at the 80-knot call — and he kept going. Five minutes later, 189 people were in the Atlantic.

Warning condition

start of the roughly 20-day parked period at Puerto Plata without pitot covers — start date computed back from the report's statement that the aircraft had not flown for twenty days

20 DAYS

If uncorrected

6 February 1996 — takeoff 03:42 UTC, impact with the Atlantic about 03:47 UTC, 14 NM offshore

Read the official report: JIAA (DGAC Dominican Republic) Final Aviation Accident Report, Birgenair Flight ALW-301, 6 February 1996
ATA 34AV-49 Pitot ProbeComplacencyNormsLack Of Awareness
What happened

A Boeing 757 chartered from Birgenair sat at Puerto Plata for what investigators believed was twenty days without flying. During that period an engine inspection required a ground run — and investigators believe the engine and pitot covers were not installed before or after the test. The aircraft was then returned to service without the pitot-static verification recommended by the manufacturer's maintenance procedures for a lengthy time on the ground. On the night takeoff, the captain's airspeed indicator was dead at the first officer's "80 knots" call; the captain elected to continue. In the climb, the blocked left pitot line made his indicator read ever-higher airspeed, triggering an overspeed warning while the aircraft was actually approaching a stall — two alarms telling opposite lies. The crew's confusion ended with the aircraft stalled and rolling into the Atlantic about five minutes after brake release. The wreckage — and the pitot tube — were never recovered; the report states the exact reason for the obstruction was never determined, and that the probable source was mud and/or debris from a small insect introduced into the pitot tube while the aircraft was on the ground.

Why it matters

The report's honesty is part of the lesson: the investigators concluded the obstructed pitot tube was not the probable cause — the crew's failure to recognize and recover was — but named maintenance practices as a contributing factor in exact terms: not installing the pitot system covers while the aircraft was on the ground, and the failure to perform return-to-service tests of the pitot/static system after a lengthy time on the ground (JIAA final report, §2.3). Had the recommended verification been done, the report says, the blockage may have been discovered and corrected before flight. A pitot cover costs almost nothing; its absence, uncorrected by the return-to-service check, put a sensor failure in front of a crew at night with 189 aboard. The popular "mud-dauber wasp nest" detail is not in the report's wording — the report says only "a small insect", and marks the cause of blockage as undetermined.

Control sequence
  1. Install pitot and probe covers whenever the aircraft is parked beyond the manufacturer's short-stay limit — storage procedures start on day one, not when someone remembers.
  2. Ground runs do not suspend storage protection: covers come off for the run and go back on afterwards, as logged steps.
  3. Return-to-service after prolonged parking requires the manufacturer's pitot-static system verification — it exists precisely to catch what settled in the tubes.
  4. Record cover installation and removal in the aircraft's paperwork so a missing cover is a visible discrepancy, not a silent nothing.
  5. Brief crews that any airspeed anomaly at the low-speed calls after ground storage is a reject-and-inspect item — the pitot-static system is guilty until proven clean.
How often

Frequency is not quantified in public sources — but 1996 alone saw two fatal Boeing 757 pitot-static accidents eight months apart, Birgenair in February and Aeroperú in October, the second occurring before bulletins prompted by the first had reached operators (JIAA final report; DGAT Peru AIB report, conclusions).

Consequences

Erroneous and diverging airspeed indications from the captain's blocked pitot line drove autopilot and autothrottle responses and an overspeed warning while actual speed decayed; the aircraft stalled and struck the Atlantic about 14 NM offshore roughly five minutes after takeoff. All 189 aboard — 13 crew, 176 passengers — died; the aircraft was destroyed on impact, and the wreckage including the pitot tubes was never recovered (JIAA final report, §1.1–1.2).

Evidence gate: publish only after verification

  • The aircraft was believed not to have flown for twenty days, and investigators believe the engine and pitot covers were not installed before or after the engine ground test run in that period. (JIAA final report, §2.3) (JIAA final report, §2.3)cited
  • It was returned to service without the manufacturer's recommended pitot-static verification — a check the report says may have discovered and corrected the blockage before flight. (JIAA final report, §2.3) (JIAA final report, §2.3)cited
  • The report words the blockage source exactly: probable source mud and/or debris from a small insect; exact reason never determined — the tubes were lost with the wreckage. (JIAA final report, §2.3) (JIAA final report, §2.3)cited

ExperienceLearn it, live it

Coming soon

EON Life Simulation

Walk into the accident and practise freely, no score. The physics decides, unscripted.

Checking your score

Assessment & certificateProven under pressure