Clogged Static Port: The Frozen Altimeter, Alternate Static Procedure, and the Aeroperú Lesson
Updated: Sep 26
The altimeter is a primary flight instrument that tells a pilot how high the aircraft is above mean sea level. Because it relies entirely on static pressure from the pitot-static system, a blockage of the static port can cause the altimeter to provide misleading or completely incorrect information. And here's what makes it uniquely dangerous: unlike a blocked pitot (which makes the airspeed read an obvious zero, or move in a suspicious way), a blocked static port makes the altimeter look absolutely normal — a stable, readable, believable number that simply stops being true. Pilots trust it because there's nothing visibly wrong with it. In 1996, that exact failure killed 70 people on Aeroperú Flight 603.
This post covers static port blockage in practical depth: what happens and why the altimeter freezes, the effects on the VSI and airspeed, why it's more insidious than a pitot blockage, how to recognize it, the alternate static source procedure and corrections, GPS altitude as a cross-check (and its limits), partial blockages and leaks, and the accident that defines the hazard.
Study this full length lesson (video, podcast, flashcards, and quiz) here: Full Length Lesson >
A Quick Review: How the Altimeter Normally Works
The altimeter measures altitude by sensing static air pressure.
The mechanism:
Static pressure enters the instrument CASE
Sealed aneroid wafers expand or contract with the pressure changes
Mechanical linkages translate the movement into an altitude indication
Static pressure drives it
The pressure relationship:
Static pressure DECREASES as altitude increases (wafers expand → higher reading)
Static pressure INCREASES as altitude decreases (wafers contract → lower reading)
As long as static pressure freely enters, the altimeter tracks altitude accurately
The normal operation
(For the full altimeter mechanism, types of altitude, and cold-weather errors, see our altimeter post.)
What Causes Static Port Blockage
The causes, expanded — and why they're harder to catch.
Common causes:
Ice formation in visible moisture (a flight hazard)
Water intrusion (rain, washing)
Debris or dirt (accumulated contamination)
Tape or covers left in place after maintenance (the Aeroperú cause)
Insects (less common, but possible)
Paint or wax (from detailing)
Why static ports are harder to preflight than the pitot tube:
Static ports are FLUSH-MOUNTED on the fuselage (not protruding like the pitot)
Small and easy to overlook
Often there are TWO (one on each side of the fuselage)
Tape over a flush port is visually subtle
Easy to miss
The maintenance-tape hazard:
During washing, painting, or maintenance, static ports are often TAPED to keep water/paint out
If the tape isn't removed, the ports are blocked
The tape can be nearly invisible (especially if painted over or a similar color)
This is exactly what happened to Aeroperú 603
A real, documented killer
The preflight imperative:
Physically inspect BOTH static ports
Look for tape, dirt, insects, or obstructions
Run a finger over them if unsure
After maintenance, be especially thorough
The catch
No static port heat (usually):
Unlike the pitot tube (which has pitot heat), static ports typically have NO heat
So ice on the static ports can't be cleared in flight
The alternate static source is the in-flight remedy
Prevention and the alternate source
What Happens When the Static Port Becomes Clogged
The core failure, expanded.
The trapped pressure:
When the static port blocks, static pressure is TRAPPED in the system
At the pressure that existed at the MOMENT of blockage
From that point forward, the system can't sense pressure changes
Frozen pressure
The consequence:
The altimeter no longer receives changing pressure
It cannot sense climbs or descents
It's stuck at the blockage-moment reading
No response to altitude
Altimeter Behavior: The Frozen Indication
The specific behavior, expanded.
The altimeter FREEZES:
Stuck at the indicated altitude where the blockage occurred
Subsequent climbs or descents do NOT change the indication
The aircraft may be climbing or descending significantly — the altimeter doesn't respond
A frozen number
The worked example:
Aircraft cruising at 5,000 feet
The static port becomes blocked by ice
The pilot descends to 3,000 feet
Altimeter indication: still 5,000 feet
Actual altitude: 3,000 feet
A 2,000-foot error
The terrain-clearance danger:
Without recognizing the failure, the pilot believes they have 2,000 more feet of terrain clearance than they actually do
Descending further compounds it
CFIT risk
The core hazard
The predictability:
The behavior is CONSISTENT and PREDICTABLE (frozen)
Once you recognize it, it's diagnosable
But it must be recognized
Predictable if caught
Why the Frozen Altimeter Is More Insidious Than a Pitot Blockage
A comparison worth making explicitly.
The pitot blockage (for contrast):
Scenario 1: the airspeed reads ZERO (obviously wrong)
Scenario 2: the airspeed moves in an odd way (increasing in a climb — suspicious if you're watching)
Either way, something looks OFF
Detectable oddity
The static blockage:
The altimeter shows a STABLE, READABLE, PLAUSIBLE altitude
Nothing looks wrong — it's a normal-looking number
It's just... not changing
No visual oddity
Why this is worse:
A stable altitude reading looks like GOOD instrument behavior (steady = normal)
Pilots trust a stable reading
The failure is invisible unless you notice the LACK of change
You have to notice an absence, not a presence
Harder to detect
The "absence of change" detection problem:
Detecting a frozen instrument requires noticing that it ISN'T changing when it should
Harder than noticing a wrong value
Requires active cross-checking (comparing to the VSI, pitch, power)
The subtle failure
The trust trap:
Because the altimeter appears stable and readable, pilots may trust it LONGER than they should
The stability is deceptive
A frozen altimeter is trusted until something else reveals the truth (terrain, ATC, GPS)
The danger
Effects on the Other Pitot-Static Instruments
The full picture — a static blockage affects all three.
The Vertical Speed Indicator (VSI):
Reads ZERO immediately
Indicates no climb or descent regardless of actual vertical movement
(No pressure change reaches the diaphragm/case)
Stuck at zero
The VSI as a clue:
A VSI reading ZERO while you're clearly climbing or descending (pitch, power, visual cues) is a strong static-blockage clue
The most telling indicator
Combined with a frozen altimeter, diagnostic
Your best cue
The Airspeed Indicator (ASI):
Becomes INACCURATE (it compares pitot to the TRAPPED static)
CLIMB: typically reads LOWER than actual airspeed
DESCENT: typically reads HIGHER than actual airspeed
Erroneous but not frozen
Why the ASI errors go that direction:
Climbing: actual ambient static drops, but the trapped static is HIGHER
The ASI uses the (higher) trapped static as its reference
This makes the pitot-static difference SMALLER → lower indicated airspeed
Descending: the reverse (larger difference → higher reading)
The trapped-reference effect
The three-instrument pattern:
Altimeter: FROZEN
VSI: ZERO
ASI: erroneous (low in a climb, high in a descent)
All three affected — the signature of a static blockage
The diagnostic value of the pattern:
A pitot blockage affects ONLY the airspeed
A static blockage affects ALL THREE
So: airspeed alone wrong → pitot; all three wrong → static
The differential diagnosis
How to Recognize a Blocked Static Port
The recognition cues, expanded.
The cross-check cues:
The altimeter does NOT change with pitch or power adjustments
The VSI remains at ZERO despite obvious climbs or descents
The airspeed behaves inconsistently with known pitch-and-power settings
Disagreement between altitude, visual cues, and GPS altitude
The "altimeter doesn't respond" cue:
You pitch up (or down) and the altimeter doesn't move
The most direct cue
Pitch changes should change altitude
A frozen response
The VSI-zero cue:
You're clearly descending (nose down, power reduced, terrain rising in the windscreen)
But the VSI reads zero
A strong indicator
The best cue
The visual cross-check (VFR):
In VFR, look outside: are you actually climbing/descending?
Compare to the instruments
The visual truth
Available in VMC
The GPS altitude cross-check:
Many GPS units display GPS altitude
Compare to the altimeter
A significant, persistent disagreement suggests a static problem
A useful cross-check (with caveats — below)
The ATC cross-check:
ATC sees your Mode C altitude (which comes from the encoder, also fed by static!)
IMPORTANT: a static blockage also affects the Mode C altitude ATC sees
So ATC may report an altitude matching your frozen altimeter (both wrong)
ATC may NOT catch it (a critical limitation)
Don't rely on ATC to catch it
The Mode C caveat (important):
The altitude encoder uses STATIC pressure (like the altimeter)
A static blockage freezes the Mode C altitude too
So ATC sees the same frozen altitude
ATC may say "altitude verified" when both are wrong
A real hazard (Aeroperú demonstrated this)
The scan discipline:
Instrument scan discipline is the primary defense
Cross-check the altimeter, VSI, pitch, power, and visual/GPS
Notice the absence of change
The defense
GPS Altitude as a Cross-Check (and Its Limits)
An important nuance the basic treatment mentions but doesn't qualify.
The value:
GPS altitude is INDEPENDENT of the pitot-static system
So it's a valid cross-check for a static blockage
A significant disagreement flags the problem
Independent reference
The critical limitation:
GPS altitude is GEOMETRIC altitude (height above the WGS-84 ellipsoid / a geoid model)
The altimeter shows PRESSURE altitude (corrected to MSL via the altimeter setting)
These are DIFFERENT references
They normally differ by some amount (often 50-200+ feet, varying with conditions)
Why they normally differ:
The altimeter is pressure-based (affected by actual pressure and temperature)
GPS is geometric (satellite geometry)
Non-standard pressure/temperature makes the pressure altitude differ from the true geometric altitude
A normal disagreement exists
The practical use:
Don't expect them to match exactly
Look for a LARGE, GROWING disagreement (hundreds of feet, increasing)
A frozen altimeter vs. a changing GPS altitude is the telltale
Trend, not exact match
The best GPS cue:
If the GPS altitude is CHANGING but the altimeter is FROZEN, that's diagnostic
The changing vs. frozen comparison
Not the absolute values
The behavior difference
The IFR caution:
GPS altitude is NOT approved for IFR altitude reference (the altimeter is)
Use it as a cross-check/situational awareness only
Not for flying assigned altitudes
A diagnostic aid
The Alternate Static Source: Procedure and Corrections
Here's the operational depth the basic treatment gestures at: the actual procedure and the specific corrections.
What it is:
A valve (usually in the cockpit, on the panel or under it) that opens the static system to CABIN air
Substitutes cabin static pressure for the blocked outside static
Restores static input to the instruments
The in-flight remedy
The procedure:
Recognize the static blockage (frozen altimeter, zero VSI, erroneous airspeed)
Locate and OPEN the alternate static source valve
Note the momentary instrument jumps (the VSI will jump — see below)
Apply the POH corrections (the altimeter and airspeed will read HIGH)
Cross-check with GPS altitude and visual references
Fly with the corrections in mind
Consider declaring an emergency if altitude awareness is compromised
The corrections (why it reads high):
Cabin static pressure is usually LOWER than the outside static pressure
(Air flowing over/around the fuselage creates a slight venturi effect, lowering cabin pressure)
Lower static pressure "looks like" a higher altitude to the altimeter
The altimeter reads HIGHER than actual
The airspeed reads HIGHER than actual
Account for both
The specific magnitude:
The exact error varies by aircraft (and is in the POH)
Often 50-100+ feet on the altimeter, and several knots on the airspeed
The POH provides the correction (check YOUR aircraft)
Aircraft-specific
The VSI jump:
When you OPEN the alternate static source, the VSI momentarily JUMPS (shows a climb)
Because the sudden pressure change (to lower cabin pressure) looks like a rapid climb
A transient (not a real climb)
Then it settles and works normally
The "you're actually lower and slower" takeaway:
With the alternate static source, the altimeter reads HIGH → you're actually LOWER than indicated
The airspeed reads HIGH → you're actually SLOWER than indicated
Both in the conservative-caution direction
Fly accordingly (add margin)
The unpressurized last resort — break the VSI glass:
In an UNPRESSURIZED aircraft with NO alternate static source
You can BREAK THE GLASS of the VSI
This vents the static system to the cabin (an improvised alternate static source)
The VSI becomes inoperative, but the altimeter and ASI work (with the cabin-static errors)
A genuine emergency technique
Know it exists
Why break the VSI (and not the altimeter):
The VSI is the LEAST critical of the three
Breaking it sacrifices the least important instrument
The altimeter and ASI (more critical) then function
The best trade
The pressurized caution:
Do NOT use this technique in a pressurized aircraft (cabin pressure is very different from ambient)
The errors would be large and unpredictable
Pressurized aircraft have proper alternate static systems
Unpressurized only
Partial Static Blockage and Static Leaks
A scenario the basic treatment doesn't cover.
Partial blockage:
The static port is PARTIALLY blocked (restricted, not sealed)
Static pressure changes reach the instruments SLOWLY (lagging)
The altimeter lags behind actual altitude changes
The VSI under-reads
A subtle, sluggish failure
Why it's harder to detect:
The instruments still respond (just slowly)
Not obviously frozen
Requires noticing the sluggishness
Subtle
The static leak (the opposite problem):
A LEAK in the static system (inside the cabin)
The system senses CABIN pressure (partially) instead of outside static
Similar to having the alternate static source partially open
The altimeter/airspeed read slightly high
A different failure
Why a leak matters:
A leak in an unpressurized cabin causes errors like the alternate static source (reads high)
Detected during the pitot-static inspection (leak check)
The 24-month IFR inspection tests for leaks
Why the inspection exists
The inspection connection:
The IFR pitot-static inspection (91.411, every 24 calendar months) includes a LEAK CHECK
Verifies system integrity
Catches leaks before they cause errors
The maintenance defense
Pilot Actions If Static Blockage Is Suspected
The response, expanded.
Immediate response:
Do NOT rely on the altimeter alone
Use ATTITUDE and POWER to control flight
Cross-check with:
GPS altitude (if available)
Visual references (VFR)
Known pitch-and-power settings
Terrain awareness
Open the alternate static source:
If equipped, activate it
Note the corrections (altimeter and airspeed read high)
Restores usable (if slightly erroneous) indications
The primary remedy
The attitude-and-power fallback:
Attitude + power = performance
Known combinations produce known results
Level flight: cruise power, level attitude
Use them
The fundamental backup
IFR considerations:
Activate the alternate static source
Follow the abnormal procedures (POH)
Advise ATC (and note that ATC's Mode C altitude may ALSO be wrong)
Consider declaring an emergency if altitude awareness is compromised
Request a visual approach or vectors to VMC if possible
The "tell ATC" nuance:
Advise ATC of the static problem
IMPORTANT: your Mode C altitude may be frozen too (ATC sees the same wrong altitude)
ATC can't verify your altitude with the encoder
They may be able to help other ways (terrain, vectors, another aircraft's report)
Communicate clearly
Getting to VMC:
If in IMC with a static failure, getting to VMC (visual conditions) restores visual altitude awareness
A priority
Request assistance
Visual reference
The terrain priority:
With a frozen altimeter, terrain clearance is the top concern
Climb if uncertain (away from terrain)
Use known safe altitudes (MSA, MEA)
Err high
The Aeroperú 603 Accident: The Defining Case
The accident that makes this topic urgent — worth knowing in detail.
The accident (October 1996):
Aeroperú Flight 603, a Boeing 757, departed Lima, Peru at night over the Pacific
During maintenance/cleaning, the STATIC PORTS had been covered with adhesive TAPE
The tape was NOT removed before flight (and wasn't caught in preflight — it was dark, and the tape was subtle on the polished fuselage)
The aircraft took off with blocked static ports
What the crew experienced:
Immediately after takeoff, the crew received conflicting and false indications
The AIRSPEED and ALTITUDE readings were erroneous (trapped static)
They received a false "RUDDER RATIO" and other warnings
As they climbed, the frozen static made the airspeed read low and the altitude read low
They received overspeed warnings AND (later) false low-altitude/terrain warnings
The crew couldn't determine their actual altitude or airspeed
The critical confusion:
The crew asked ATC for their altitude
ATC's radar showed the aircraft's MODE C altitude — which came from the same blocked static system
So ATC reported an altitude that was also WRONG (matching the frozen/erroneous reading)
The crew believed they were higher than they actually were
Both the crew and ATC were working from the same false data
The outcome:
Believing they were at a safe altitude (around 9,700 feet indicated) while actually much lower
The aircraft struck the ocean
All 70 aboard died
A preventable maintenance/preflight failure
The lessons:
Static ports must be verified clear in preflight (especially after maintenance)
Maintenance tape/covers must be removed and verified (a documented procedure)
A static blockage corrupts ALL pressure instruments (altimeter, VSI, airspeed, AND Mode C)
ATC's Mode C altitude comes from the same static system — it's NOT an independent check
GPS altitude (if available) is an independent cross-check
The alternate static source is the remedy — use it
Getting to VMC / visual reference restores awareness
The modern relevance:
Led to improved maintenance procedures (covers with flags, verification checklists)
Reinforced the preflight static-port check
A permanent case study
Why this topic matters
The connection to your preflight:
Every time you check the static ports, you're checking for the Aeroperú failure mode
It takes two seconds
It has killed 70 people
Check them
Static Blockage in Glass Cockpits
The modern picture, expanded.
The technology:
Static pressure is sensed electronically (Air Data Computer)
Altitude is computed digitally
Displayed on the PFD
Digital processing
The failure is the same:
A blocked static port still causes incorrect altitude (the ADC gets bad pressure)
Physics unchanged
Same failure
Technology doesn't eliminate physics
The detection advantages:
Failure FLAGS or alerts may appear (but not always)
Dual-source aircraft may have comparator warnings ("ALT MISCOMPARE")
Some systems compare with GPS altitude and alert
Better detection (sometimes)
The caution:
Don't assume the glass cockpit will catch it
Single-source GA systems may not
Understand the mechanical principles
Pilot recognition still required
Why This Knowledge Matters
The stakes, expanded.
Many serious accidents have involved static system failures:
Aeroperú 603 (the definitive case)
Others involving frozen or erroneous altitude
Often with maintenance or preflight causes
A documented killer
Pilots who understand static blockage can:
Detect failures quickly (notice the absence of change)
Avoid trusting frozen instruments
Use the alternate static source correctly (with its corrections)
Maintain safe terrain clearance
Make correct decisions under pressure
The turn-an-emergency-into-a-problem value:
Instrument knowledge turns a system failure into a MANAGEABLE PROBLEM instead of an emergency
Recognition + correct response = survivable
Ignorance + trust = accident
The difference
Conclusion
When the static port becomes clogged, the altimeter freezes at the altitude where the blockage occurred, providing no further indication of climbs or descents — while the VSI reads zero and the airspeed becomes erroneous (low in a climb, high in a descent). The altimeter may look perfectly normal, stable, and readable. It is simply no longer telling the truth, and that deceptive normality is exactly what makes it more insidious than a pitot blockage.
The response is to recognize the pattern (frozen altimeter, zero VSI, odd airspeed), open the alternate static source (remembering that altitude and airspeed will then read HIGH), fly attitude and power, and cross-check with GPS altitude and visual references — while remembering that ATC's Mode C altitude comes from the same blocked system and is not an independent check.
Aeroperú 603 is the permanent reminder: tape over two small flush ports, missed in a night preflight, corrupted every pressure instrument on a Boeing 757 and killed everyone aboard. Check your static ports. In aviation, altitude awareness is critical — and knowing how it can be lost is a key part of keeping it.
On the Written Test and Checkride
Static blockage appears on tests and checkride orals. The most commonly tested topics:
The altimeter FREEZES at the blockage altitude
The VSI reads ZERO
The airspeed reads LOW in a climb, HIGH in a descent
That a static blockage affects ALL THREE instruments (vs. pitot affecting only airspeed)
The alternate static source (reads HIGH on altitude and airspeed)
The break-the-VSI-glass last resort (unpressurized)
Quick Reference
The Failure:
Static pressure TRAPPED at the blockage-moment value
The system can't sense pressure changes
Affects ALL static instruments
Instrument Behavior:
Instrument | Behavior |
Altimeter | FREEZES at blockage altitude |
VSI | Reads ZERO |
Airspeed | Climb: reads LOW; Descent: reads HIGH |
The Differential Diagnosis:
Airspeed alone wrong → PITOT blockage
All three wrong (frozen alt, zero VSI, odd ASI) → STATIC blockage
The Worked Example:
Blocked at 5,000 ft, descend to 3,000 ft
Altimeter still reads 5,000 ft
Actual: 3,000 ft (2,000 ft error — CFIT risk)
Causes:
Ice, water, debris, insects
Tape/covers left after maintenance (the Aeroperú cause)
Flush-mounted and easy to miss (usually TWO ports)
No static port heat (usually)
Recognition Cues:
Altimeter doesn't change with pitch/power
VSI reads ZERO despite climbing/descending (best cue)
Airspeed inconsistent with pitch/power
GPS altitude CHANGING while the altimeter is FROZEN
The Mode C Caveat (critical):
The altitude encoder uses the SAME static system
A static blockage freezes ATC's Mode C altitude too
ATC is NOT an independent check
(This killed Aeroperú 603)
GPS Altitude Cross-Check:
Independent of pitot-static (valid cue)
BUT: GPS is GEOMETRIC altitude; the altimeter is PRESSURE altitude
They normally differ (50-200+ feet)
Look for a frozen altimeter vs. a CHANGING GPS altitude (the behavior, not the values)
Not approved for IFR altitude reference
Alternate Static Source:
Recognize the blockage
OPEN the alternate static valve
Expect a momentary VSI JUMP
Apply POH corrections
Cross-check GPS/visual
Altimeter reads HIGHER than actual (you're LOWER)
Airspeed reads HIGHER than actual (you're SLOWER)
Cabin static is lower than outside static
Unpressurized Last Resort:
No alternate static source → BREAK THE VSI GLASS
Vents static to the cabin
VSI becomes inoperative; altimeter and ASI work (with cabin-static errors)
NOT in pressurized aircraft
Pilot Response:
Don't rely on the altimeter alone
Attitude + power = performance
Open the alternate static source
Cross-check GPS altitude and visual references
Advise ATC (noting Mode C may be wrong too)
Get to VMC if possible
Err HIGH for terrain
Declare if altitude awareness is compromised
Aeroperú 603 (1996):
Maintenance TAPE over the static ports, not removed
All pressure instruments (and Mode C) corrupted
ATC reported the same false altitude (not independent)
Crew flew into the ocean; 70 died
Lesson: check the static ports every preflight
Key Principle:
A clogged static port freezes the altimeter at the blockage altitude, zeros the VSI, and makes the airspeed read low in a climb and high in a descent — all three affected (vs. a pitot blockage, which affects only airspeed). The frozen altimeter looks perfectly normal, which makes it more insidious. Open the alternate static source (altitude and airspeed will read HIGH), fly attitude and power, and remember ATC's Mode C comes from the same blocked system. Aeroperú 603 proves why you check the static ports.
Study Full Aviation Courses:
wifiCFI's full suite of aviation courses has everything you need to go from brand new to flight instructor and airline pilot! Check out any of the courses below for free:
Study Courses:
Checkride Lesson Plans:
Teaching Courses:
Author: Nathan Hodell
CFI, CFII, MEI, ATP, Creator and CEO
Nathan is an aviation enthusiast with thousands of hours of flying and dual instruction over the past 15+ years. Through his aviation career he has been able to earn his ATP, fly as an airline pilot, own/operate flight schools, and create and host wifiCFI.