The first time I jumped into Utah's Wasatch Mountains after dark, I thought I had my gear dialed. I'd done 70 night skydives over flat terrain, my altimeter was set to the local DZ QNH, and I'd memorized my standard 2500ft AGL main deployment callout. What I didn't account for was how drastically mountain terrain messes with barometric pressure readings, and how impossible it is to spot a 7000ft snow-covered ridge when you're staring into pitch black with only a tiny canopy light to guide you.
I pulled my main at what I thought was 2500ft AGL, only to realize 10 seconds later I was 300ft lower than my altimeter claimed, drifting straight for a rock outcropping I couldn't see. I had to make a sharp, low turn to avoid impact, and landed hard in a snowbank 50ft from the ridge. That close call taught me something no flat-terrain night jump ever did: default altimeter settings will get you killed over mountain valleys, and customizing your gear for the unique demands of this jump is non-negotiable.
Mountain valleys create wild microclimates that throw off standard barometric altimeter readings by 200 to 500ft, even when you use the most up-to-date regional QNH from ATC. Night vision limits make it impossible to cross-reference altitude with terrain cues, and rapid pressure changes as you descend from a high jump run into a low valley amplify analog altimeter lag. The settings below are the result of years of testing, near-misses, and conversations with mountain jump pilots and riggers who specialize in high-altitude, night terrain jumps.
Ditch Regional QNH for On-Site Calibration
The biggest mistake skydivers make on mountain jumps is setting their altimeter to the QNH (barometric pressure setting) of the nearest regional airport, or even the DZ's home airport if it's located in a different valley 10+ miles away. Mountain ranges create isolated pressure zones: a valley 15 miles from your jump site can have a barometric pressure 3-4hPa (hectopascals) different from your drop zone, which translates to a 250-350ft error in your altimeter reading. That error is manageable on flat terrain, where you can cross-check with visual cues, but at night over mountains, a 300ft error can put you on a collision course with a ridge you can't see.
For night mountain jumps, skip the remote QNH entirely. Before you board the plane, verify the exact elevation of your primary landing zone (PLZ) with a GPS or official topographic map (download offline maps beforehand if you're jumping in a remote area with no cell service). Then adjust your altimeter's barometric setting until it reads exactly your PLZ's known MSL elevation when you're standing on it. This ensures your altimeter is calibrated to the local pressure zone of your jump area, not a distant valley.
If you're jumping from a high mountain ridge rather than a valley airport, calibrate your altimeter to the jump run elevation before you exit the plane, cross-checking with the pilot's altimeter to confirm you're reading the correct altitude for your exit point. This avoids the common error of pulling your main at the wrong altitude because your altimeter was calibrated to the low valley DZ instead of the high ridge jump run.
Customize Alerts for Terrain Awareness, Not Just Deployment
Default altimeter alerts are built for flat terrain: a generic 1000ft warning, 500ft warning, and 200ft deployment alert. Over mountain valleys, these generic settings ignore the biggest risk: drifting into high terrain you can't see at night.
First, set a dedicated terrain proximity alert on your digital altimeter (or GPS watch, if your altimeter lacks terrain mapping) to trigger at 1000ft above the highest ridge or peak in your jump corridor. For context: if the highest point in your jump area is 7500ft MSL, set this alert to go off at 8500ft MSL. Even if you're disoriented, turned around, or drifting off course toward high ground, you'll get an audio (and vibration, if you enable it) warning long before you're at risk of impact. For analog altimeter users, mark that 1000ft buffer above your highest terrain with a small glow-in-the-dark dot during your pre-jump gear check, so you can do a quick visual check if you suspect you're off course.
Next, adjust your deployment alerts to be relative to your PLZ elevation, not fixed MSL values. Set your main deployment warning to trigger at 2500ft AGL over your PLZ, not a fixed 3000ft MSL that might be only 500ft AGL if you're landing in a low basin. For your reserve automatic activation device (AAD), set it to trigger at 1000ft AGL above the highest terrain in your jump area, not your PLZ. This means if you drift toward a ridge while under a malfunctioning main, your reserve will deploy 500-1000ft earlier than a standard AAD setting, giving you enough time for the reserve to open before you hit the slope.
Add a secondary low-altitude downdraft alert too: set your altimeter to beep and vibrate if you're descending faster than 1000ft per second below 5000ft MSL. Nighttime valley winds often create sudden, powerful downdrafts right above the tree line, and this alert will warn you if you're being pushed toward terrain faster than you expect.
Tweak Display Settings to Protect Night Vision
A bright white altimeter display is worse than useless at night: it constricts your pupils, makes it impossible to spot other skydivers or faint terrain cues, and leaves you with temporary flash blindness that can last 10-15 seconds after you glance at it.
Disable auto-brightness entirely, and set your digital altimeter to its dimmest red backlight mode. Red light has the smallest impact on pupil dilation, so you can glance at your altitude without ruining your night vision. Turn off any white backlight or strobe features entirely, unless you're using a strobe strictly for visibility to other jumpers, in which case set it to the dimmest possible setting.
Set your display to show both MSL (mean sea level) altitude and PLZ-relative AGL (above ground level) at all times, no toggling required. At night, it's easy to lose track of whether you're over a high ridge or low valley, so being able to cross-check both numbers in a split second helps you avoid dangerous altitude errors.
If you use an analog altimeter, skip the LED light stickers entirely. Instead, apply a thin layer of glow-in-the-dark paint (charged with a flashlight before the jump) only to the 1000ft, 500ft, and 200ft tick marks. This lets you read your altitude without a flashlight, no bright lights required.
Adjust for Pressure Sensor Lag
All altimeters have a small amount of lag as they adjust to changing barometric pressure, but this lag is drastically amplified on mountain jumps, where you'll descend 5000ft or more in 60 seconds as you drop from a high jump run into a low valley. Analog altimeters can lag 200-400ft during rapid descents, reading higher than your actual altitude, which leads to late deployments and close calls with terrain.
If you're using an analog altimeter, or an older digital model with a slow pressure sensor, add a 300ft buffer to all your minimum altitude callouts. If you normally deploy your main at 2500ft AGL over flat terrain, bump that to 2800ft AGL for night mountain jumps to account for lag. For digital altimeters with fast sensors, a 100ft buffer is sufficient, but test your gear's lag in a controlled environment (like a high tower or low-altitude practice jump) before your jump to confirm its accuracy at rapid descent speeds.
Cold temperatures at high altitude also worsen lag, so if you're jumping in temperatures below 40°F (4°C), add an extra 100ft buffer to your deployment altitude.
Night skydiving over mountain valleys is one of the most magical experiences you can have as a skydiver: the glow of tiny valley towns below, the silence of freefall broken only by the wind, the view of snow-capped ridges lit by the moon. But that magic comes with real risk, and a misconfigured altimeter is the fastest way to turn a dream jump into a nightmare. These settings aren't one-size-fits-all: adjust them based on the specific range you're jumping, your experience level, and your gear's capabilities. But the core rule stays the same: never rely on default settings for terrain that's as unpredictable as mountain valleys after dark. Your altimeter is your only reliable reference for altitude when you can't see the ground---make sure it's set to keep you safe, not just give you a number.