IFR Cruising Altitudes: The Hemispheric Rule, Lowest Usable Flight Level, RVSM, MEA Changes, and Altitude Strategy
Updated: 3 days ago
Choosing the correct cruising altitude under Instrument Flight Rules is more than a regulatory checkbox — it affects safety, efficiency, ATC coordination, fuel burn, oxygen requirements, icing exposure, and passenger comfort. Many pilots memorize the basic hemispheric rule early in training, but fewer understand the structure underneath it: why FL180 isn’t always a usable altitude, what actually changed when RVSM arrived, exactly when you start climbing at an MEA increase, and how ATC’s altitude assignments relate to the rule you learned. Understanding the why behind IFR altitudes is what turns a memorized table into real en route competence.
This post covers IFR cruising altitudes in practical depth: what an IFR cruising altitude is and who chooses it, the 91.179 hemispheric rule and where it applies, flight levels and the lowest usable flight level, RVSM done correctly, the minimum IFR altitudes (MEA, MOCA, MRA, MCA, MAA, OROCA, and the 91.177 off-route rule), how to handle MEA changes at a fix, how ATC actually assigns altitudes (including wrong-way, cruise, and block clearances), altitude strategy with a worked example, and the common mistakes.
Study this full length lesson (video, podcast, flashcards, and quiz) here: Full Length Lesson >
What an IFR Cruising Altitude Is
An IFR cruising altitude is the altitude (or flight level) at which you fly the en route portion of an IFR flight — in controlled airspace, the altitude assigned by ATC; in uncontrolled airspace, the altitude you select under the hemispheric rule.
Why IFR altitudes are controlled:
Maintain vertical separation between aircraft that can’t see each other
Ensure terrain and obstacle clearance in IMC
Support traffic flow management
Keep aircraft within radar and radio coverage
All four at once
The fundamental IFR rule:
In controlled airspace, you fly the altitude ATC ASSIGNS — nothing else — unless you receive an amended clearance or are exercising emergency authority (91.123)
You may request a different altitude; ATC decides
The hemispheric rule tells ATC (and you) what the “normal” altitudes are, but the assignment governs
Assigned altitude is the law
The VFR contrast:
VFR: you choose your altitude (hemispheric + 500) above 3,000 AGL, subject to cloud clearance
IFR: ATC assigns it (in controlled airspace), and you fly it precisely
Different degrees of freedom
IFR trades freedom for separation
The IFR Hemispheric Rule (91.179)
The structure that organizes IFR altitudes, with where it actually applies.
The rule, by magnetic course:
Magnetic course 000° through 179° (eastbound): ODD thousands — 3,000, 5,000, 7,000, 9,000 … FL190, FL210, etc.
Magnetic course 180° through 359° (westbound): EVEN thousands — 2,000, 4,000, 6,000, 8,000 … FL180, FL200, etc.
Whole thousands — no “+500”
“East is odd” (and VFR adds 500 to it)
(Preserve the existing hemispheric-rule table image here.)
Magnetic COURSE, not heading:
The rule is based on your magnetic COURSE (the direction of your intended track over the ground, corrected for variation)
NOT your magnetic heading (which includes the wind correction angle)
A course of 175° with a 10° right crab (heading 185°) is still EASTBOUND → odd
A common error
The key difference from VFR:
VFR (91.159): odd + 500 (east), even + 500 (west), above 3,000 AGL
IFR (91.179): odd (east), even (west), whole thousands
The 500-foot offset is what keeps VFR and IFR traffic vertically separated
Two interleaved systems
Where the rule APPLIES to you directly — uncontrolled airspace (91.179(b)):
In Class G (uncontrolled) airspace under IFR, YOU must fly the hemispheric altitude for your course (except while in a holding pattern of two minutes or less, or while turning)
No ATC assignment exists there
The rule is a regulation on the pilot
Mandatory in Class G
Where the rule is ATC’s framework — controlled airspace (91.179(a)):
In controlled airspace, you fly the altitude ATC assigns
ATC generally assigns hemispheric-appropriate altitudes, but is NOT bound to
ATC may assign a “wrong-way” altitude (an even altitude eastbound) for traffic or sector reasons — and that’s a valid clearance
If assigned, fly it
The “wrong-way altitude” reality:
“Climb and maintain 6,000” when you’re eastbound is legal if ATC assigns it
Don’t argue it or “correct” it — ATC has separated you from traffic at that altitude
Read it back and fly it
The assignment overrides the rule
Filing the altitude:
File a hemispheric-appropriate altitude for your course (it’s what ATC expects and what makes the clearance “as filed” more likely)
For a route with multiple course changes, file for the predominant direction (or the first leg) and expect changes
A direct GPS route has a single course — file for that
File smart, expect amendments
Flight Levels and the Transition at 18,000 Feet
Above 18,000 feet MSL, altitudes become flight levels — and the transition has a detail the basic treatment misses.
The transition:
At and above 18,000 feet MSL, set the altimeter to 29.92 inHg (1013.25 hPa) — the standard setting
Altitudes are then called FLIGHT LEVELS: FL180 = 18,000, FL240 = 24,000, FL350 = 35,000
All aircraft above the transition use the same reference, so separation is consistent regardless of local pressure
Standardization at altitude
Why 29.92:
Local altimeter settings vary across the country (29.50 in a low, 30.40 in a high)
At altitude, with aircraft crossing large regions quickly, a common reference eliminates the pressure differences
Everyone measures from the same datum
Separation depends on it
The altimeter-setting procedure:
CLIMBING through 18,000: set 29.92 at 18,000
DESCENDING through FL180: set the local altimeter setting before leaving FL180 (ATC will provide it)
A standard callout: “transition altitude, 29.92” / “transition level, altimeter 29.XX”
A critical, easy-to-forget step
The hemispheric rule continues:
Eastbound: odd flight levels (FL190, FL210, FL230 …)
Westbound: even flight levels (FL180, FL200, FL220 …)
Same rule, new units
Up to FL290 at 1,000-foot intervals, then RVSM (below)
Class A airspace:
18,000 MSL to FL600 is Class A
IFR only — no VFR
Transponder and ADS-B required
Instrument rating required
The Lowest Usable Flight Level (91.121) — The Detail Everyone Skips
FL180 is not always a usable altitude. This is a classic tested point the original doesn’t cover.
The problem:
Flight levels are referenced to 29.92
If the actual local pressure is LOWER than 29.92, an aircraft at “FL180” (reading 18,000 on a 29.92 altimeter) is actually BELOW 18,000 feet true altitude
Meanwhile, an aircraft at 17,500 on the LOCAL altimeter setting is at a true 17,500
The two could be less than 500 feet apart — or overlap
The reference mismatch creates a separation gap
The fix — the lowest usable flight level (91.121(b)):
When the altimeter setting is below 29.92, the LOWEST usable flight level is raised so that it still provides the required separation from aircraft below the transition altitude
The regulation steps the lowest usable flight level up in 500-foot increments, because each 0.50 inHg of pressure is roughly 500 feet of altitude:
Current altimeter setting | Lowest usable flight level |
29.92 or higher | FL180 |
29.91 through 29.42 | FL185 |
29.41 through 28.92 | FL190 |
28.91 through 28.42 | FL195 |
28.41 through 27.92 | FL200 |
27.91 through 27.42 | FL205 |
27.41 through 26.92 | FL210 |
Reading it:
Each 0.50 inHg drop in the setting raises the lowest usable flight level by 500 feet
With a 29.60 setting, FL180 is NOT usable — the lowest usable is FL185
With 29.20, the lowest usable is FL190
With 28.70, the lowest usable is FL195
The practical consequence — what ATC can actually assign:
Cruise altitudes are assigned in whole thousands under the hemispheric rule, so the lowest ASSIGNABLE cruise level is the next whole flight level at or above the lowest usable one
At 29.60 (lowest usable FL185): FL180 is off the table — eastbound gets FL190, westbound gets FL200
At 29.20 (lowest usable FL190): eastbound FL190, westbound FL200
At 28.70 (lowest usable FL195): eastbound FL210, westbound FL200
If you file FL180 on a low-pressure day, expect FL190 or FL200 depending on your direction
The transition altitude doesn’t move:
You still set 29.92 climbing through 18,000 feet
It’s the lowest usable (and assignable) FLIGHT LEVEL that rises, not the altitude at which you change the setting
Two different things
The memory aid:
“Below 29.92, add 500 feet for every half inch”
29.42 → FL185; 28.92 → FL190; 28.42 → FL195
Count down in halves, count up in 500s
The pattern
A checkride question:
“The altimeter setting is 29.50. What’s the lowest usable flight level?” → FL185 (29.50 falls in the 29.91–29.42 band)
“What’s the lowest cruise level ATC would assign you eastbound?” → FL190 (the first odd whole level at or above FL185)
Know both the regulatory answer and the operational one
RVSM: 1,000-Foot Separation at High Altitude
Reduced Vertical Separation Minimum — what it is and what it changed.
Before RVSM:
Above FL290, altimeter accuracy limitations required 2,000-foot vertical separation
Eastbound: FL290, FL330, FL370, FL410 (odd levels at 4,000-ft intervals)
Westbound: FL310, FL350, FL390 (the alternating levels)
Half the altitudes were unused
RVSM (in the US since 2005):
Between FL290 and FL410 inclusive, vertical separation is REDUCED to 1,000 feet for aircraft that meet the RVSM standards
The normal hemispheric rule applies: eastbound odd (FL290, 310, 330, 350, 370, 390, 410), westbound even (FL300, 320, 340, 360, 380, 400)
Doubled the usable altitudes in the most fuel-efficient band
The “reduced” in the name is the 2,000 → 1,000 change
Above FL410 (non-RVSM spacing):
Above FL410, 2,000-foot separation returns
Eastbound: FL450, FL490 … (odd, at 4,000-ft intervals)
Westbound: FL430, FL470 …
The old structure persists up high
The equipment and authorization requirement:
To operate in RVSM airspace (FL290–FL410), the aircraft must meet the RVSM equipment and altitude-keeping standards: two independent altimetry systems, an altitude-alerting system, an autopilot with altitude hold meeting the standard, and a transponder
Historically, the operator also needed a specific RVSM authorization (an LOA or OpSpecs)
Since 2019, aircraft equipped with qualifying ADS-B Out that meet the RVSM performance standards may operate in RVSM airspace WITHOUT that separate authorization — the FAA monitors altitude-keeping performance through ADS-B instead
Operators without qualifying ADS-B Out still need the authorization
Non-RVSM aircraft generally cannot cruise in FL290–FL410, though ATC may accommodate climbs and descents through it, and certain operations (DoD, ferry flights) by arrangement
For the GA pilot:
Understand that RVSM = 1,000-ft spacing between FL290 and FL410, NOT 2,000
Know that the 2,000-ft structure applies above FL410
Know that RVSM requires the equipment standards (and, without qualifying ADS-B Out, an authorization)
If you fly a turbocharged piston or a turboprop into the flight levels, you’ll live with this
The summary:
Altitude band | Separation | Structure |
Below FL290 | 1,000 ft | Odd east / even west |
FL290–FL410 (RVSM) | 1,000 ft | Odd east / even west (RVSM-compliant aircraft only) |
Above FL410 | 2,000 ft | East FL450, 490 …; West FL430, 470 … |
Minimum IFR Altitudes: The Complete Set
Choosing or accepting an altitude isn’t just about direction — it must meet the minimum altitude requirements that guarantee terrain and obstacle clearance. Here’s the full family.
MEA — Minimum En Route Altitude:
The lowest published altitude on an airway segment that guarantees BOTH obstacle clearance AND navaid signal reception
Published on IFR en route charts (the bold number on each segment)
The default minimum for the segment
Clearance (1,000 ft non-mountainous / 2,000 ft mountainous) plus signal
MOCA — Minimum Obstruction Clearance Altitude:
The lowest altitude on a segment that guarantees OBSTACLE clearance — but VOR navaid reception only within 22 NM of the VOR
Shown with an asterisk (*) below the MEA on charts (e.g., *3200)
Lower than the MEA (sometimes by thousands of feet)
The 22 NM limit is a VOR signal-reception limit (91.177(a)(2)): it applies to aircraft navigating the segment by VOR. Aircraft navigating by GPS/RNAV have the required signal throughout the segment and may use the MOCA anywhere along it
MRA — Minimum Reception Altitude:
The lowest altitude at which an off-route navaid (for an intersection/fix) can be received
Shown with an “R” flag at the fix
May be higher than the MEA
Only needed to identify that specific fix
MCA — Minimum Crossing Altitude:
The lowest altitude at which you may CROSS a specific fix when continuing in a specified direction (usually where the MEA increases ahead)
Shown with an “X” flag at the fix
Ensures you’re already climbing to meet the higher MEA with terrain clearance
Governs the altitude AT the fix
MAA — Maximum Authorized Altitude:
The HIGHEST usable altitude on a segment
Published where navaid signal overlap (two VORs on the same frequency) could cause interference above that altitude
Rare but real
The ceiling, not the floor
MTA — Minimum Turning Altitude:
A minimum altitude for a turn at a fix, where the turn geometry creates an obstacle-clearance concern
Shown with a flag at the fix
A specialized minimum
OROCA — Off-Route Obstruction Clearance Altitude:
A grid-based altitude (in each 1° × 1° quadrangle on the en route chart)
Provides 1,000 ft (non-mountainous) or 2,000 ft (mountainous) above the highest obstruction in the grid
NO navaid or communication coverage guarantee
For off-route (direct) flying and emergencies — similar to the sectional’s MEF but with built-in clearance
MVA — Minimum Vectoring Altitude:
ATC’s minimum altitude for radar vectoring in a given area
Not published to pilots (on ATC’s charts)
Often BELOW the MEA (radar can see obstacles that the airway design can’t rely on)
What ATC uses when they vector you
MIA — Minimum IFR Altitude:
ATC’s minimum altitude in non-radar/en route sectors
Similar concept to MVA for Center airspace
Also not published to pilots
The 91.177 off-route rule (direct routes with no MEA):
When operating IFR off a published route (a GPS direct route, say), you must fly at least:
1,000 feet above the highest obstacle within 4 NM of your course (non-mountainous areas)
2,000 feet above the highest obstacle within 4 NM of your course (designated mountainous areas)
The same clearance values the MEA is built on, applied by the pilot
The OROCA is a convenient way to satisfy it (it’s built on these numbers per grid)
Your responsibility on direct routes
Handling MEA Changes at a Fix
A real operational skill the original doesn’t cover: what to do when the MEA changes along your route.
When the MEA INCREASES at a fix (ahead of you):
Begin the climb to the higher MEA immediately after passing the fix (you may stay at the lower MEA until the fix)
UNLESS an MCA is published at that fix — then you must CROSS the fix at or above the MCA (meaning you must start climbing BEFORE the fix to arrive at the MCA)
The MCA exists precisely because terrain rises so fast that starting the climb at the fix isn’t enough (91.177(b))
No MCA: climb at the fix; MCA published: be at it when you cross
The MCA example:
Your segment MEA is 5,000; the next segment’s MEA is 9,000; the fix has an MCA of 7,000 (eastbound)
You must cross the fix at or above 7,000 — so you start climbing before the fix
After the fix, continue climbing to 9,000
The MCA bridges the gap
When the MEA DECREASES at a fix:
You may descend to the lower MEA after crossing the fix (not before)
And you may descend to the MOCA where it applies (within 22 NM of the VOR if navigating by VOR; anywhere on the segment if navigating by GPS)
Don’t descend early
Cross, then descend
In controlled airspace with ATC:
Your ASSIGNED altitude governs; ATC won’t assign you below the MEA on an airway under your own navigation (they’ll climb you before the increase)
If ATC hasn’t climbed you and you’re approaching an MEA increase, ASK — “Request climb to [MEA] for the MEA at [fix]”
Don’t bust the MEA because ATC forgot
You’re responsible for the MEA; ATC should be too, but verify
When ATC vectors you:
On radar vectors, ATC uses the MVA (often below the MEA) and assumes responsibility for terrain clearance
You may be assigned an altitude below the airway MEA while being vectored — that’s legal
When ATC says “resume own navigation,” you’re back to the published altitudes — make sure you’re at or above the MEA
Vectors = ATC’s altitude; own navigation = the chart’s altitude
The MEA-gap note:
Some segments are marked “MEA GAP” — a stretch where navaid reception isn’t assured even at the MEA
Navigate by dead reckoning (or GPS) through the gap
The obstacle clearance is still provided
A heads-up on the chart
How ATC Actually Assigns IFR Cruising Altitudes
The regulation sets the framework; traffic flow determines what you get.
Controllers consider:
Opposing-direction traffic at the hemispheric altitudes
Sector boundaries and handoff altitudes (Center sectors are stratified by altitude)
Your aircraft type and performance (a 172 and a Citation get different altitudes)
Arrival and departure streams at nearby airports
Weather deviations in progress
Letters of agreement between facilities (fixed altitudes for certain routes)
The practical reality:
You may REQUEST an altitude (on the flight plan or by radio)
ATC may assign something different — and that’s final unless you request again
Expect STEP CLIMBS on longer flights (3,000 → 5,000 → 7,000 as traffic and sectors permit)
Turbojets and turboprops often get the higher altitudes; pistons fill in below
The first assignment is rarely the final one
The initial clearance:
“Climb and maintain 5,000, expect 9,000 ten minutes after departure”
5,000 is your ASSIGNED altitude (fly it)
9,000 is the EXPECT altitude (do NOT climb to it on your own)
The “expect” is informational — and it’s your lost-communications altitude
The “expect” altitude is not authorized:
You climb to the expect altitude ONLY when ATC assigns it (“climb and maintain 9,000”)
Climbing to it on your own because “they said expect” is an altitude bust
The only time you self-climb to it is lost comms (at the expected time or when reaching the fix)
Expect ≠ cleared
Requesting a different altitude:
“Request 7,000 for winds” / “Request lower for icing” / “Request higher for turbulence”
Give the reason — it helps ATC prioritize
ATC will approve, deny (“unable, traffic”), or offer an alternative
Ask; the worst answer is “unable”
Cruise clearances:
“Cruise 7,000” is a special clearance: it authorizes you to fly at ANY altitude from the minimum IFR altitude up to and including 7,000, climbing and descending at your discretion
It also authorizes you to proceed to and begin an approach at the destination without further clearance
Once you REPORT leaving an altitude in a cruise clearance, you may NOT return to it without a new clearance
Used in non-radar environments and at quiet destinations
Block altitudes:
“Maintain block 6,000 through 8,000” authorizes you to operate anywhere in that block
Used for turbulence (you can ride the bumps), for training maneuvers, or for weather
Request it when you need vertical flexibility
ATC protects the whole block
VFR-on-top:
An IFR clearance to fly at VFR altitudes (odd/even + 500) in VMC, typically on top of a cloud layer, while remaining on an IFR flight plan
You must maintain VFR visibility and cloud clearance, fly a VFR altitude appropriate to your course, and still comply with the IFR rules that apply (MEAs, clearances, position reports)
ATC does not provide IFR separation to VFR-on-top aircraft — you receive traffic advisories as workload permits and are responsible for see-and-avoid, exactly as a VFR aircraft would be
Requested by the pilot; not available in Class A
Choosing the Best IFR Cruising Altitude: Strategy
Experienced IFR pilots think beyond “legal” and weigh performance, weather, and workload.
Aircraft performance:
Normally aspirated: loses roughly 3% power per 1,000 ft; true airspeed gains roughly 2% per 1,000 ft; the sweet spot is usually 6,000–10,000 ft where TAS gains offset power loss
Turbocharged: holds power to the critical altitude; higher is often faster and more efficient (and gets you above weather)
Oxygen: required above 12,500 ft after 30 min (crew), above 14,000 continuously, provided to passengers above 15,000 — the oxygen rule often caps the altitude choice for unpressurized aircraft
Know your aircraft’s efficient band
Winds aloft:
Check the winds aloft forecast for several altitudes
A tailwind may justify a higher (or lower) altitude than performance alone suggests
A strong headwind at altitude may favor staying low even at a TAS penalty
Winds often decide it
A worked example:
180 NM eastbound leg, normally aspirated single, 115 KTAS at 7,000, 120 KTAS at 11,000
Winds aloft: 7,000 — 250° at 15 (a 15-kt tailwind); 11,000 — 250° at 35 (a 35-kt tailwind)
At 7,000: groundspeed ~130 kt → 1:23; at 11,000: ~155 kt → 1:10
The higher altitude saves 13 minutes and a couple of gallons, but costs a longer climb (more fuel) and approaches the oxygen threshold
Net: 11,000 wins on this leg if the climb is practical and you’re comfortable near 12,500 — the winds, not the performance, decided it
Weather:
Icing: stay out of the clouds in the icing band (0°C to about −15°C); choose an altitude above the tops or below the bases, or in air warmer than freezing — the freezing level and the cloud layers determine the safe altitudes more than anything else
Tops vs. bases: on top is smooth and visual; below the bases may be bumpy but ice-free in warm air
Convective activity: altitude doesn’t help; deviate laterally
Turbulence: mechanical turbulence is worst low; ride above it if the layer is shallow
Workload:
Lower altitudes: more traffic, more frequency changes, more Approach-control handoffs, more weather
Higher altitudes: fewer handoffs (Center), smoother air, but oxygen, longer climbs/descents, and stricter planning
Choose the altitude that matches your attention budget for the flight
Workload is a real factor
Terrain:
In mountainous areas, the MEA may be high (9,000–13,000+)
Oxygen, performance, and icing all interact at those altitudes
Plan the altitude around the terrain, then check the other factors
The MEA may choose for you
The decision sequence:
What’s the MEA/OROCA for the route? (the floor)
What does oxygen allow? (the practical ceiling for unpressurized)
Where is the icing? (which altitudes are safe)
What are the winds? (which safe altitude is fastest)
What does performance favor? (the efficient band)
Is it hemispheric-appropriate? (odd/even for the course)
File it; expect ATC to amend it
IFR Altitudes Outside the United States
Internationally, the rules are ICAO-based with variations.
Common differences:
Transition altitude: varies widely (3,000–6,000 ft in much of Europe; 18,000 is a US convention) — the altitude where you switch to 29.92/1013 differs by country and sometimes by airport
Transition level: the lowest usable flight level, published per region
Metric flight levels: China and a few other countries use meters, with a conversion table
Semicircular rule variations: some regions use the same odd/even structure; a few use a quadrantal system
RVSM applicability: nearly global now, but with regional differences in equipment and authorization
The practical rule:
Check the AIP (Aeronautical Information Publication) for the country and the Jeppesen/chart notes
Brief the transition altitude and level before every international flight
Don’t assume 18,000 feet or 29.92
Different country, different rules
Common IFR Altitude Mistakes
Confusing magnetic HEADING with magnetic COURSE when applying the hemispheric rule (course governs; the wind correction doesn’t change it)
Treating the “expect” altitude as authorized and climbing to it early (it’s informational and for lost comms only)
Forgetting to set 29.92 climbing through 18,000 (or the local setting descending through FL180)
Filing FL180 on a low-pressure day (the lowest usable flight level may be FL185 or higher, so FL190/FL200 is the lowest assignable)
Believing RVSM means 2,000-foot spacing (it means 1,000 feet between FL290 and FL410)
Descending below the MEA on an airway without being on vectors or in a MOCA segment where it applies
Starting a climb at an MEA increase when an MCA required you to be higher at the fix
Descending at an MEA decrease before crossing the fix
Forgetting oxygen rules above 12,500/14,000/15,000 when choosing a high altitude
Flying a direct route without checking the OROCA or applying the 91.177 4-NM rule
Returning to a vacated altitude in a cruise clearance without a new clearance
Assuming ATC is separating you from traffic while VFR-on-top (they aren’t — you are)
Not asking ATC for a climb when approaching a higher MEA they haven’t yet assigned
Checkride Questions — With Answers
“What are the IFR cruising altitudes?”
By magnetic course: 000–179° (eastbound) odd thousands; 180–359° (westbound) even thousands (91.179). Whole thousands, no +500. Mandatory in uncontrolled airspace; ATC’s framework in controlled airspace, where the assigned altitude governs.
“The altimeter setting is 29.50. What’s the lowest usable flight level?”
FL185, per the 91.121 table (29.91 through 29.42 → FL185). Each 0.50 inHg below 29.92 raises it 500 feet. Operationally, since cruise levels are whole thousands, the lowest level ATC would assign is FL190 eastbound or FL200 westbound.
“What is RVSM?”
Reduced Vertical Separation Minimum: 1,000-foot vertical separation between FL290 and FL410 (instead of the old 2,000 feet), for aircraft meeting the RVSM equipment and performance standards. Above FL410, 2,000-foot separation returns. Since 2019, qualifying ADS-B Out can substitute for a separate RVSM authorization.
“What’s the difference between MEA and MOCA?”
Both guarantee obstacle clearance; the MEA also guarantees navaid reception along the whole segment, while the MOCA guarantees VOR reception only within 22 NM of the VOR. You may fly at the MOCA within 22 NM of the facility when navigating by VOR — or anywhere on the segment when navigating by GPS (91.177).
“When the MEA increases at a fix, when do you climb?”
Immediately after passing the fix — unless an MCA is published, in which case you must cross the fix at or above the MCA (start climbing before the fix).
“Can ATC assign you an altitude below the MEA?”
Yes — when radar vectoring, ATC uses the MVA (often below the MEA) and assumes terrain responsibility. In a MOCA segment, the MOCA applies. Under your own navigation on an airway, you must be at or above the MEA.
“What is a cruise clearance?”
Authorization to fly at any altitude from the minimum IFR altitude to the cruise altitude, climbing and descending at your discretion, and to proceed to and begin an approach at the destination without further clearance. Once you report leaving an altitude, you can’t return to it without a new clearance.
“Does ATC separate you from other traffic when VFR-on-top?”
No. VFR-on-top aircraft do not receive IFR separation — only traffic advisories as workload permits. You are responsible for see-and-avoid, while still complying with the applicable IFR rules.
“What do you do with an ‘expect’ altitude?”
Nothing, until ATC assigns it — except in lost communications, when you climb to it at the expected time or fix.
Final Thoughts
IFR cruising altitudes are a blend of regulation, airspace design, and practical ATC management. The hemispheric rule — odd east, even west, whole thousands — is the framework, mandatory in uncontrolled airspace and the default ATC works from everywhere else. Above 18,000 feet, flight levels standardize the reference at 29.92, with the subtlety that FL180 itself isn’t usable on a low-pressure day (the 91.121 table steps the lowest usable flight level up 500 feet per half inch), and with RVSM squeezing the separation to 1,000 feet between FL290 and FL410 for compliant aircraft.
Beneath every altitude choice sit the minimums — MEA, MOCA, MCA, OROCA, and the 91.177 off-route rule — that keep you clear of the ground in IMC, and the procedures for climbing at an MEA increase that make those minimums work. On top of the minimums sits strategy: oxygen, icing, winds, performance, and workload, weighed together to pick the altitude that’s both legal and smart. Understanding the why behind all of it helps you communicate with ATC, plan safer and more efficient flights, anticipate altitude changes, and reduce workload — the difference between passing a checkride and becoming a confident instrument pilot in the real world.
On the Written Test and Checkride
IFR altitudes appear on every instrument written and oral. The most commonly tested topics:
The 91.179 hemispheric rule (course-based, odd east/even west, whole thousands)
Flight levels, 29.92, and the lowest usable flight level table (91.121)
RVSM (1,000 ft, FL290–FL410, equipment standards)
MEA vs. MOCA (22 NM for VOR), MRA, MCA, MAA, OROCA
The 91.177 off-route minimums (1,000/2,000 ft within 4 NM)
MEA change procedures (climb at the fix, MCA, descend after)
The “expect” altitude, cruise clearances, and VFR-on-top
Quick Reference
The Hemispheric Rule (91.179):
Magnetic COURSE 000°–179° (eastbound): ODD thousands (3,000, 5,000 … FL190, FL210)
Magnetic COURSE 180°–359° (westbound): EVEN thousands (2,000, 4,000 … FL180, FL200)
Whole thousands (VFR adds +500)
Course, NOT heading
Mandatory in Class G; ATC’s framework in controlled airspace (assigned altitude governs; wrong-way assignments are valid)
Flight Levels:
At/above 18,000 MSL: set 29.92; altitudes become FLs (FL180 = 18,000)
Climbing through 18,000: set 29.92; descending through FL180: set local
18,000–FL600 is Class A (IFR only)
Lowest Usable Flight Level (91.121):
Altimeter setting | Lowest usable FL |
≥ 29.92 | FL180 |
29.91–29.42 | FL185 |
29.41–28.92 | FL190 |
28.91–28.42 | FL195 |
28.41–27.92 | FL200 |
27.91–27.42 | FL205 |
27.41–26.92 | FL210 |
+500 ft per 0.50 inHg below 29.92
Lowest ASSIGNABLE cruise level = next whole FL at/above the lowest usable (29.60 → eastbound FL190, westbound FL200)
The transition altitude (18,000 / set 29.92) does not move
RVSM:
FL290–FL410: 1,000-ft separation (odd east / even west) — RVSM-compliant aircraft only
Equipment: dual altimetry, altitude alerter, altitude-hold autopilot, transponder
Since 2019: qualifying ADS-B Out replaces the separate authorization; without it, an LOA/OpSpecs is still required
Above FL410: 2,000-ft separation (east FL450, 490 …; west FL430, 470 …)
Below FL290: 1,000 ft, normal rule
Minimum IFR Altitudes:
Term | Meaning |
MEA | Obstacle clearance + navaid reception for the whole segment |
MOCA (*) | Obstacle clearance; VOR reception only within 22 NM (GPS users may use it anywhere on the segment) |
MRA (R flag) | Altitude to receive an off-route navaid for a fix |
MCA (X flag) | Altitude you must be at when CROSSING a fix (MEA rising ahead) |
MAA | Maximum authorized altitude (signal interference above) |
MTA | Minimum turning altitude at a fix |
OROCA | Grid altitude: 1,000 ft (non-mtn) / 2,000 ft (mtn) above obstacles; no nav/comm guarantee |
MVA / MIA | ATC’s vectoring/en route minimums (not published to pilots; often below MEA) |
91.177 Off-Route Rule:
1,000 ft above the highest obstacle within 4 NM of course (non-mountainous)
2,000 ft (designated mountainous)
OROCA satisfies it per grid
MEA Changes at a Fix:
MEA increases: climb immediately AFTER the fix — unless an MCA is published, then cross the fix AT the MCA (start climbing before)
MEA decreases: descend only AFTER crossing the fix
On vectors: ATC’s MVA governs (may be below MEA); “resume own navigation” → back to published altitudes
Approaching a higher MEA with no climb assigned → ASK
ATC Assignments:
“Climb and maintain 5,000, expect 9,000 …” → fly 5,000; 9,000 is informational (and for lost comms)
Expect ≠ cleared
Request altitudes with a reason (“for winds/icing/turbulence”)
Wrong-way altitudes are valid if assigned
Step climbs are normal
Special Clearances:
Cruise [altitude]: any altitude from the minimum IFR altitude to that altitude, at your discretion; proceed to and begin the approach at the destination; once you report leaving an altitude, no return without a new clearance
Block [X through Y]: operate anywhere in the block (turbulence, weather)
VFR-on-top: IFR clearance at VFR altitudes (+500) in VMC; maintain VFR cloud clearance and comply with applicable IFR rules; no IFR separation provided (advisories only; you see-and-avoid); not in Class A
Altitude Strategy (in order):
MEA/OROCA floor
Oxygen ceiling (12,500/14,000/15,000)
Icing band (0° to −15°C in cloud) — stay out
Winds aloft (often decisive)
Performance band (NA: 6,000–10,000; turbo: higher)
Hemispheric-appropriate for the course
File; expect amendments
Key Principle:
IFR altitudes follow the 91.179 hemispheric rule — odd east, even west, by magnetic course — mandatory in uncontrolled airspace and ATC’s framework everywhere else, where the assigned altitude governs. Above 18,000 feet, flight levels use 29.92, and the 91.121 table raises the lowest usable flight level 500 feet for every half inch the altimeter setting falls below 29.92 (29.50 → FL185); RVSM gives 1,000-foot spacing from FL290 to FL410 for compliant aircraft. Every altitude must respect the MEA (or the MOCA where it applies, or the 91.177 off-route rule), with climbs started at the fix for an MEA increase unless an MCA says sooner. Then choose strategically: oxygen, icing, winds, performance, workload.
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.