How to fly the RNAV (GPS) approach into Aspen/Pitkin County

An RNAV (GPS) approach can make entry into Aspen/Pitkin County look deceptively simple: a blue course, a sequence of waypoints and a runway lined up on the display. The terrain around Aspen does not become simpler because the navigation is electronic. At roughly 7,820 feet, KEGE combines high elevation, mountain weather, steep surrounding ground and performance changes that demand a disciplined cockpit workflow. Learn more about How To Conduct A Thorough Preflight Inspection On A Cirrus Sr22.

This guide explains how to fly the RNAV (GPS) approach into Aspen/Pitkin County as an Australian-trained pilot, from planning through landing and a missed-approach contingency. It is educational material rather than an operational clearance. The current FAA chart, airport information, NOTAMs and aircraft flight manual take precedence, and an appropriately rated, current pilot should make the final decisions. Learn more about Contact.

Australian habits are helpful: domestic IFR flight plans go through Airservices Australia, instrument privileges are governed by CASA Part 61, and GPS approaches are often labelled RNAV (GNSS). Pilots are accustomed to QNH, feet for altitude and kilometres on the road, although US charts normally use inches of mercury and miles for visibility. Pilots travelling from Sydney, Melbourne, Brisbane or Perth should also allow time to manage jet lag and the transfer from Denver’s commercial airport to a general-aviation training base.

Plan the route and charted procedure

Start with the current FAA sources rather than an app, a simulator or an old plate. Obtain the KEGE Instrument Approach Plate and Airport/Facility Diagram, then read the applicable notes. Confirm the procedure title, runway designator, final course, required GPS service, fixes, restrictions, minimum altitudes and missed-approach routing. An RNAV label alone does not show whether LPV, VOR/DME or another minima line applies to your equipment and the current chart.

Plan the arrival through the published transition, and use the procedure only as shown on the current source. Enter the departure, arrival and approach waypoints with their exact charted names, then check that the navigation database contains them. Program altitude and speed constraints rather than relying on a visual guess. Compare the planned track with obstacle data, especially around the river valleys and high ground east and south of the aerodrome; a straight magenta line may not be the published or protected path.

Supplementary aviation study resources can support revision, but they must not replace the FAA material. For an Australian operator, distinguish the US trip from the Australian flight-plan process: a domestic IFR flight in Australia goes to Airservices Australia, while a US plan is filed with the FAA. Confirm that your licence, medical and instrument rating satisfy FAA requirements, including 14 CFR Part 91 and any visiting-pilot or foreign-licence requirements.

Check weather, terrain and performance

Check METAR and TAF information, pilot reports, the local ATIS and any en-route weather source. Winds, visibility, ceiling, temperature, dew point, altimeter setting and RVR can all affect whether an RNAV approach is practical. Thunderstorms can produce windshear and rapidly changing winds, while freezing levels, icing and mountain-wave turbulence may extend well beyond the immediate approach corridor. Compare conditions with the chart minima and the published missed-approach requirements.

At field elevation near 7,820 feet, aircraft performance can change sharply with altitude, temperature and weight. A warm summer day can place density altitude far above the published field elevation, reducing available thrust and increasing takeoff and landing distance. Calculate from the current aircraft flight manual and performance data, check weight and balance, and obtain the runway condition. Snow, standing water, ice or a contaminated surface may further change the margins.

Set the altimeter in the units shown for that specific source. Australian pilots normally work with QNH in hectopascals and use feet for altitude, but a US approach plate will normally require an inch-of-mercury setting. Visibility and weather information may also use different units. Verify the mode, value and trend on the PFD, because a correct-looking pressure setting with the wrong unit or reference can create a dangerous altitude error.

Prepare the cockpit and navigation system

Confirm that the navigation database is current for the intended route and that the receiver has the service required by the selected minima. Check applicable GPS NOTAMs, receiver fault annunciations and an integrity indicator such as RAIM or an approved equivalent. LPV approaches depend on the required augmentation; a receiver that displays a valid approach does not prove that every required service is available. Read the aircraft manual for database currency and exact annunciation meanings.

Before departure, the aeroplane still needs the usual disciplined walk-around. For a Cirrus SR22, Independence Aviation’s Cirrus preflight inspection provides a detailed reference for control surfaces, fuel, oil and airframe items, with the aircraft manual and maintenance release taking precedence. A GPS installation cannot compensate for a mechanical issue, an expired inspection or a fuel-state error.

Configure the route while electrical power is stable and avoid programming a complex approach until the departure is settled. Set the course and flight director functions to match the approved aircraft configuration, check heading and altitude references, and verify that the selected frequencies correspond to departure and en-route ATC, Aspen approach and local ATIS as applicable. Record the assigned transponder code and altitude in a visible place without relying on memory alone.

Brief the approach and missed approach

Brief the approach as a sequence of tasks rather than a single “fly the magenta line” instruction. State the transition, fixes, restrictions, course, final approach fix, descent profile and whether the controlling minimum is a minimum descent altitude or decision altitude. For a cockpit capable of LPV, identify whether the active source provides lateral guidance, vertical guidance or both. Note the applicable speed references, missed-approach trigger and expected visual reference.

The missed approach deserves the same attention as the planned landing. Trace its published track, altitude, heading and first turn, if specified, then identify terrain that could constrain an early correction. Aspen’s surrounding mountains make a low improvised turn hazardous. If the required visual reference is not available at the specified point, discontinue the approach and follow the published missed approach unless ATC directs an alternative. Fly it at the published missed-approach rate until clearance permits an alternative.

For Australian pilots, compare the US chart’s minima, terrain and obstacle information with the procedures familiar from an Australian RNAV (GNSS) approach. Australian charts may use different naming conventions and units, so reading the plate aloud catches assumptions before the aircraft is committed. If continuing toward remote mountain aerodromes, carry equipment suited to the exposure, register the emergency beacon and plan communications gaps before departure.

Fly the RNAV (GPS) approach

On clearance, load and activate the approach. Confirm that the flight-management system shows the correct runway, transition and final approach fix. Check the active leg against the paper or electronic chart, and verify bearing-to-fix, desired track and CDI/HSI presentation. Use TO/FROM annunciation and flight-director mode flags as cross-checks; never interpret a centred needle alone as proof that the correct approach is loaded.

Before the descent, compare position, distance to the fix and estimated time at its altitude with the plan. Recheck winds, altimeter setting and any changed weather, then brief the altitude at which each segment begins. Descend only in accordance with the chart and clearance, and avoid allowing the GPS display to pull the aircraft ahead of a published restriction.

At the final approach fix, confirm that the active approach is armed, the course is centred and the published altitude has been reached. Continue to the runway if the required visual reference is established and the aircraft is in a position from which a normal descent and landing can be made. Otherwise, remain at or above the applicable minimum and execute the missed approach.

During a coupled descent, remain active and be ready to disconnect the autopilot and fly manually if the displayed guidance or aircraft response does not agree with the chart. For a visual approach, use runway lights, the airport diagram and natural features that were briefed, while accounting for illusions caused by rising terrain, a sloping runway perspective or reduced night cues. After touchdown, maintain directional control and follow the published taxi route.

Handle a missed approach or equipment problem

If the weather deteriorates before the approach is committed, request an ATC delay, vector or alternate as appropriate. Once the missed approach is required, execute the published procedure at its specified altitude and speed, then contact ATC as directed. Do not descend toward a valley because the approach appears closer than it is or attempt an unbriefed turn.

If the navigation system, audio or electrical system fails, announce the failure and request assistance. Follow the approved aircraft abnormal procedures and published departure or diversion guidance, maintain a safe altitude and use only the backup navigation aids permitted by the flight manual and operating rules. Paper charts, the compass, onboard terrain awareness and radio communication can support that decision.

Treat any unstable approach as an event requiring a reset. After a missed approach or systems failure, reassess weather, fuel, terrain, performance and the cause of the disruption before attempting another approach. Keep passengers briefed and do not let schedule pressure shape the safety decision.

Manage the aircraft and continue mountain training

Before landing, retain a go-around plan. After touchdown, leave margin for taxi fuel and braking, then plan for the return leg. High altitude reduces aircraft performance, and a return flight may involve a longer climb than expected at sea level. Review any maintenance concerns before departure and calculate fuel for the actual route, diversion and expected holding rather than a direct great-circle estimate.

Pilots comparing ownership, rental or charter options can review Independence Aviation’s pilot support services across its Centennial Airport and Rocky Mountain Metro Airport bases. The company operates as a Cirrus Platinum Training Center and provides aircraft and hangar management, charter, rental, advanced proficiency, mountain-flying instruction and mentoring that support instrument and mountain currency.

Australia’s owner-managed general aviation market also includes shared hangars and contracted maintenance, with Australian work governed by CASA Part 43 and Part 145. US maintenance records, approvals and insurance requirements differ, so an Australian owner should obtain local advice before committing to a hangar, management or charter arrangement. That combination of published-procedure discipline, weather margins and aircraft-performance planning makes an RNAV arrival at Aspen a controlled mountain operation rather than a simple satellite-guided descent.