En route operations

Read the route as connected segments

An IFR en route chart shows the system the clearance uses: navigation aids, fixes, conventional/RNAV routes, courses, distances and altitude limits. Select the correct low/high chart and current legend. Verify each segment from fix to fix, including where the route changes, a facility changes over or a restriction applies. A highlighted line can hide a short high-altitude segment or a different required sensor.

Victor airways generally serve the low-altitude conventional system; RNAV T-routes use suitable approved RNAV equipment. A route designation alone does not establish aircraft eligibility. Check required approval, serviceable equipment, relevant NOTAMs and any published GNSS or ground-facility dependency. At a VOR changeover point, use the prescribed facility change; the strongest-looking signal is not a substitute for the charted navigation plan.

Keep assigned route and present position visible while configuring the next segment. Section 91.181 generally requires the airway centerline or direct course between defining fixes unless ATC authorizes otherwise, with its stated maneuvering provisions. Course changes need turn planning to remain within protected route space; honor a published fly-over requirement rather than importing a generic early turn. A direct amendment can change both terrain and navigation requirements.

AIM 5-3-4/5/6: route systems and course changes · §91.181: course to be flown · IPH Chapter 2: en route chart/fix/navigation interpretation · Current FAA en route charts and chart legends

Distinguish obstacle protection from usable navigation

The MEA is the lowest published altitude between the defining fixes that meets obstacle clearance and acceptable navigation-signal coverage requirements. It applies to the specified route segment, not to every point in the chart grid. Observe any charted reception-gap note and equipment/route condition; no single label guarantees all radio services.

The MOCA, typically marked by an asterisk on FAA low en route charts, meets obstacle clearance for the segment. For VOR navigation it assures acceptable signal coverage only within 22 NM of the VOR. Current §91.177 permits operation below the MEA down to the MOCA when applicable navigation signals are available; an aircraft using VOR is subject to that22-NM limit. Other approved suitable navigation may alter the reception issue, but the aircraft approval, route requirements and actual clearance still matter. A GPS display does not by itself authorize descent.

Example: study MEA 6,000/MOCA 4,000 on a route, with a VOR-only airplane30 NM from the relevant station. The lower number clears segment obstacles but does not establish the applicable VOR-navigation condition. Seek a usable altitude/route through ATC before treating the MOCA as an escape below icing. Verify communications and aircraft capability too.

OROCA is an off-route grid altitude providing terrain/obstruction clearance (normally1,000 feet, or2,000in designated mountainous areas). It is for situational awareness/planning/contingency; it is not assessed for navigation, ATC surveillance or communications coverage and is not a cleared direct route. MEA, MOCA and OROCA answer different questions.

§91.177(a): applicable minima and current MOCA/navigation conditions · IPH Chapter 2, Minimum IFR Altitudes/MEA/MOCA: route clearance and signal limits · AIM 4-4-9 note: OROCA purpose and coverage limits

Apply the fix and route limits in the correct direction

An MRA is a reception/fix-identification condition, not a universal terrain altitude for the surrounding area. Use any authorized suitable RNAV substitution only within its approval and procedure rules; do not assume a tablet fixes a ground-receiver limitation.

Under §91.177(b), climb to a higher minimum begins immediately after the point where it applies unless obstacles require crossing at the MCA. A published MCA requires being there at or above its value in the specified direction. Study case: the next segment's MEA is 8,000, and the eastbound MCA at the entry fix is 7,000. Plan to cross at least 7,000, then continue the required climb; arriving at 6,000 and merely beginning to climb at the fix misses the crossing condition.

An MTA can be higher than adjacent MEAs because a turning aircraft covers a different obstacle area. Read the stated incoming/outgoing route combination and hold the MTA until established on the next centerline, as required. Do not combine two safe straight segments with an unexamined turn. Request clearance clarification or an alternative when performance cannot meet the crossing or turn requirement.

§91.177(b): higher minima and MCA crossing · IPH Chapter 2, Minimum IFR Altitudes: MRA, MAA, MCA and MTA · AIM 5-3-7: specified MTA route combination and retention through the turn

Maintain the authority and conditions actually in effect

In controlled-airspace IFR level cruising flight, §91.179 uses the assigned altitude/flight level unless otherwise authorized. A favorable wind or an eastbound “odd-thousand” preference does not authorize changing it. Below18,000in uncontrolled airspace, the rule generally uses magnetic course0–179°odd thousands and180–359°even thousands, with its holding/turning exceptions. This is magnetic ground course, not wind-corrected heading.

An IFR VFR-on-top clearance permits appropriate VFR altitudes subject to restrictions; it still requires VFR weather/cloud clearance, applicable minimum IFR altitudes and IFR responsibilities. It is not IFR cancellation or an unrestricted choice to descend through cloud. Verify the precise clearance and options before requesting it.

Keep the appropriate altimeter setting and recognize that very cold conditions can make true altitude lower than indicated. Apply actual charted cold-temperature requirements and aircraft/procedure guidance when applicable; do not invent a correction from this lesson. Reassess terrain, oxygen, freezing levels, climb performance and reachable diversion/glide options when selecting or requesting an altitude.

A controller's “verify assigned altitude” question is a verification request, not an instruction to change to the number mentioned. State your actual/current assigned altitude and resolve disagreement. Maintain the clearance unless a valid amendment or necessary emergency action changes it.

§91.179: controlled/uncontrolled and VFR-on-top cruise altitude · §91.121: altimeter settings · AIM 4-4-8: VFR-on-top responsibilities · AIM 5-3-1(b): initial contact and altitude verification · AIM 5-1-17: applicable cold-temperature procedure information

Give ATC the progress information it needs

Maintain a continuous watch on the appropriate frequency unless otherwise authorized. Under §91.183 report time/altitude at designated or specifically requested points as applicable, unforecast weather, and other safety information. While under radar control only the position points specifically requested need reporting, but the weather/safety duties remain.

A solid triangle identifies a compulsory reporting point; an open triangle is on request. On a nonradar direct route, report the defining points. When ATC says “radar contact,” discontinue routine designated-point position reports unless requested. Resume them after “radar contact lost” or “radar service terminated.” A handoff by itself does not mean radar service was lost.

A complete report identifies aircraft, position, time, altitude, ETA/name of next reporting point, next succeeding point's name and relevant remarks. Type of flight plan is included when appropriate, but is not needed in an IFR report directly to Center or approach. Fictional practice: “N742FD, GROVE at one eight three two, six thousand, estimating HILL at one eight four seven, RIDGE next.” Use a measured/verified fix passage and an updated estimate.

Current AIM additional-report guidance includes leaving an assigned altitude for another, inability to achieve at least 500 feet/minute climb/descent, missed approach, arrival/leaving a hold, and filed-cruise TAS variation of 5 percent or10 knots, whichever is greater. Without radar contact, update an estimate when it is in error by more than 2 minutes in this domestic context. These specific AIM practices should be distinguished from the broader legal §91.183 requirements and any controller request.

Section 91.187 requires prompt practical reporting of navigation, approach or communications malfunctions in controlled IFR. State aircraft identity, affected equipment, impaired capability and assistance desired. For a GPS anomaly, add useful position, altitude and duration. A radio report helps ATC plan; it does not restore navigation approval or safe terrain clearance.

§91.183: continuous watch and required IFR reports · §91.187: malfunction report content · AIM 5-3-1/2/3: contact, point symbols, report contents and additional reports · IFH 10-7: position reporting examples

Use available traffic information without surrendering lookout

Section 91.113 requires vigilance to see and avoid when weather permits, whether operating IFR or VFR. ATC separation and traffic services do not display every aircraft or guarantee that a VFR airplane is known. Maintain an outside scan when possible while preserving the instrument cross-check, particularly through climbs/descents and near busy airports.

Traffic systems differ. ADS-B/TIS-B displays can omit nonparticipating traffic, have surveillance/reception/latency limits, or use incomplete altitude information. A blank display means no displayed targets, not no aircraft. A tablet traffic symbol is an advisory aid; it is not a TCAS resolution advisory or permission for an improvised avoidance maneuver based solely on relative icons.

Understand the installed system's approved traffic alerts and response procedures. If TCAS resolution-advisory capability is actually installed, use its trained aircraft procedures and inform ATC as required; do not give RA-like authority to every traffic alert. Report “negative contact” when you have not visually identified the traffic, and request assistance or clarification without claiming visual separation that you cannot maintain.

ATC workload, surveillance coverage and equipment affect advisories. Listen to the frequency and correlate a report with actual visual contact or reliable instrument information. Do not let traffic-page manipulation or fixation on one target consume attention needed to maintain the aircraft's safe flightpath.

§91.113(b): see-and-avoid vigilance when weather permits · §91.123: TCAS RA deviation and notification provisions · AIM 4-5-6/7/8/9: ADS-B, TIS-B and related traffic-system limits · AIM 4-4-14/15/16: visual separation, scanning and TCAS · AIM 5-5-10: traffic advisory pilot/controller roles

Make weather and fuel updates into decisions

Compare actual groundspeed, time, fuel consumption and usable fuel with the log. A stronger headwind increases destination and alternate fuel; a reroute can also change terrain, navigation and oxygen needs. Recalculate expected arrival, approach/diversion fuel and protected reserve while an alternative is still reachable. Request a change early instead of waiting for a reserve warning.

Use current in-flight observations, advisories, PIREPs and forecasts at relevant locations/altitudes/times. A new icing report at your escape altitude may invalidate a descent that looked safe before takeoff. A destination deterioration can require a farther alternate or a hold. ATC can assist with requests and information, but cannot guarantee a clear path through hazardous weather.

Digital weather supports strategic decisions. Check observation/valid time, display age, coverage, altitude and product meaning; processing and transmission can make the actual data older than its displayed age. Do not use delayed radar imagery to thread storm cells. Cross-check new data with other sources and aircraft indications; avoid an extended heads-down session while conditions or traffic demand monitoring.

For ground preparation of ACS V.B.S8/S9, compare two weather updates and a changed fuel log. Explain what deteriorated, which display assumptions matter, and a supported reroute/altitude/diversion decision. Identify the chart and communications action needed. Actual in-flight weather interpretation and display use require supervised practice; this lesson does not establish operational proficiency.

AIM 7-1-11 and 7-1-27: in-flight information, data limits and thunderstorm avoidance · AIM 5-5-15: minimum fuel/priority communication · ACS V.B.S8/S9: ground preparation for in-flight weather update and digital information use

FLIGHT SCENARIO

What would change your plan?