top of page

MEA vs MOCA: Understanding Minimum IFR Enroute Altitudes

When flying IFR, altitude selection is never arbitrary. Every published altitude exists to ensure obstacle clearance, navigation signal reliability, and safe aircraft separation. Two of the most commonly misunderstood altitudes on IFR enroute charts are the MEA (Minimum Enroute Altitude) and the MOCA (Minimum Obstacle Clearance Altitude).


Although they often appear close together on charts—and sometimes differ by only a few hundred feet—their purposes are distinct, and misunderstanding them can lead to lost navigation capability or regulatory violations.


This post explains what MEA and MOCA are, how they differ, and when each applies in real-world IFR flying.



Study this full length lesson (video, podcast, flashcards, and quiz) here: Full Length Lesson >


What Is the MEA (Minimum Enroute Altitude)?

The Minimum Enroute Altitude (MEA) is the lowest altitude between fixes on an IFR route that provides both:

  1. Adequate obstacle clearance

  2. Reliable navigation signal coverage


In other words, MEA is the altitude that guarantees you can:

  • Clear terrain and obstacles safely

  • Receive and use the required navaids for that segment of flight


Key Characteristics of MEA

  • Published on IFR enroute low and high altitude charts

  • Applies to a specific route segment

  • Ensures obstacle clearance (typically:

    • 1,000 feet in non-mountainous areas

    • 2,000 feet in mountainous areas)

  • Guarantees full navaid reception along the entire segment


If ATC assigns you an altitude at or above the MEA, you can expect both safe terrain clearance and reliable navigation.


What Is the MOCA (Minimum Obstruction Clearance Altitude)?

The Minimum Obstruction Clearance Altitude (MOCA) is a lower altitude option that still guarantees obstacle clearance—but with a significant limitation.


MOCA provides:

  • Obstacle clearance only

  • Navigation signal reception only within 22 NM of the navaid


Key Characteristics of MOCA

  • Usually published in smaller text beneath the MEA

  • Ensures obstacle clearance equal to MEA

  • Guarantees navaid reception only within 22 nautical miles of the facility

  • Does not guarantee navigation signal coverage for the entire route segment


Because of this limitation, MOCA is primarily used:

  • When flying close to the navaid

  • During emergency or contingency situations

  • Occasionally for radar vectors or ATC-approved operations


“Comparison table of MEA versus MOCA showing that both provide obstacle clearance, but MEA guarantees navaid signal for the entire route segment and is commonly used for normal IFR operations, while MOCA guarantees signal only within 22 NM of a navaid and is used less often.”


Why MEA Is the Default for IFR Operations

The MEA exists to support normal, predictable IFR navigation. It ensures pilots can track airways and fixes without worrying about signal loss, terrain conflicts, or unexpected dead zones.


Flying below MEA without authorization can result in:

  • Loss of VOR or NDB reception

  • Inability to identify fixes

  • Increased workload

  • Potential regulatory violations


For this reason:

  • ATC will normally assign altitudes at or above MEA

  • Pilots should plan cruise altitudes that meet or exceed MEA

  • MEA is the altitude used for lost communications procedures


Appropriate Uses of MOCA

  • You are within 22 NM of the navaid

  • ATC assigns or approves the altitude

  • You are navigating using a system that does not rely on the ground-based navaid (e.g., GPS, where authorized)

  • You are managing an emergency or abnormal situation


Important Limitation

If you fly beyond 22 NM from the facility at MOCA:

  • Navaid signal reception is not guaranteed

  • You may lose the ability to identify fixes

  • You may not meet IFR navigation requirements


This is why MOCA is not commonly assigned during routine IFR flight.


MEA, MOCA, and GPS Navigation

With modern RNAV (GPS) equipment, pilots often ask whether MOCA limitations still matter.

The answer: yes—sometimes.

  • MEA and MOCA are still based on ground-based navaid coverage

  • GPS may allow navigation below MEA if authorized and charted

  • Some routes publish MEA/GPS or MEA RNAV altitudes

  • Always verify:

    • Chart notes

    • Equipment authorization

    • ATC clearance


Unless explicitly authorized, pilots should not assume GPS eliminates MEA requirements.


Common Pilot Mistakes

Even experienced IFR pilots sometimes misunderstand these altitudes:

  • Assuming MOCA is always acceptable because it’s published

  • Forgetting the 22 NM limitation

  • Descending below MEA without clearance

  • Using MOCA during lost communications

  • Confusing MOCA with OROCA (which does not guarantee navigation or communication)


Practical Takeaway

  • MEA is your go-to IFR altitude for enroute flight

  • MOCA is a limited-use, lower altitude with navigation restrictions

  • When in doubt, fly the MEA

  • If ATC assigns an altitude below MEA, confirm obstacle and navigation clearance


Understanding the difference between MEA and MOCA isn’t just about passing an instrument checkride—it’s about making informed, safe decisions in real IFR conditions.



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:



 
 
bottom of page