
On this page
- When a Standard ILS Is Not Enough
- What Exactly Is a CAT II Approach
- The basic idea
- How to think about the categories
- CAT I vs CAT II vs CAT III A Quick Comparison
- ILS Approach Categories Compared
- What those numbers mean in the real world
- Aircraft and Airport Equipment Requirements
- What the airplane must bring
- What the airport must provide
- Pilot Training and Authorization Requirements
- Authorization is operational, not personal
- What the training is designed to prove
- What usually trips up GA pilots
- Flying the CAT II Approach Procedures and Callouts
- Before the approach starts
- From glideslope intercept to decision height
- At minimums
- Common Pitfalls and How to Avoid Them
- The traps that catch pilots
- Simple countermeasures that work
You've probably had this moment already. You launch on an IFR trip with weather that looks manageable, and by the time you're near destination, the ATIS has slid lower than you expected. A normal ILS that felt like a solid plan at departure may no longer be enough.
That's where a CAT II approach starts to matter. Not as trivia, and not as something only airline crews think about, but as a real capability for a general aviation pilot who wants to expand options safely and legally. The catch is that CAT II isn't just “a lower ILS.” It's a tightly controlled operation built on training, equipment, runway infrastructure, and strict decision-making.
When a Standard ILS Is Not Enough
A standard ILS is the workhorse of instrument flying. Most of the time, it gets the job done. But there's a narrow weather band where a pilot can be fully current, flying a sound airplane, and still have to divert because the visibility or ceiling has dropped below what a normal CAT I approach allows.
A CAT II approach exists for that band. It gives you a legal and operational path to continue an instrument approach in worse visibility than CAT I, but without stepping into the even more specialized world of CAT III. That makes it useful for ambitious general aviation pilots who want more dispatch reliability without pretending the rules are optional.

The first mental shift is this: CAT II is not a “nice to have” upgrade layered onto your instrument rating. It's a separate operating environment. The weather minimums are lower, which means your margin for guessing, improvising, or cleaning things up late is lower too.
Practical rule: If your normal IFR habits include “I'll sort that out on the way down,” they won't hold up in CAT II.
For a general aviation pilot, that's good news. The system is strict because it removes ambiguity. Either the runway is equipped, the procedures are active, the airplane qualifies, and you're authorized, or the answer is no.
That clarity matters when you're tired, single-pilot, and watching the destination weather slide. CAT II doesn't turn a bad situation into a good one. It gives a well-prepared pilot one more safe option before diverting.
What Exactly Is a CAT II Approach
A CAT II approach is a precision ILS approach designed for lower visibility operations than CAT I. The reason pilots care is simple: it lets you descend closer to the runway before you must either see the required visual references or go missed.

The basic idea
The defining numbers are what separate CAT II from the ILS you already know. Category II ILS approaches are defined by a Decision Height of at least 100 feet and a Runway Visual Range of no less than 1,200 feet, compared with CAT I requirements of a 200-foot Decision Height and 1,800-foot RVR or 550 meters, according to this CAT I and CAT II minima summary.
Those numbers aren't abstract. They describe how long you can stay on instruments before the runway environment has to appear in a form that satisfies the procedure. With CAT I, you decide earlier. With CAT II, you continue lower, which demands more precise guidance and much tighter system integrity.
Think of it this way. CAT I gets you to a point where the runway should come into view sooner. CAT II lets you stay in the instrument environment longer, so when the runway does appear, it may happen very late in the approach. That is why the procedure relies so heavily on automation, lighting, and exact callouts.
How to think about the categories
A simple way to visualize it is by altitude above the touchdown zone. CAT I is familiar territory for most instrument pilots. CAT II is a deeper commitment. You're descending to a much lower decision point, which means there's less time to transition from instruments to outside references and less room for a sloppy scan.
Here's the practical meaning:
- CAT I: Normal instrument flying for many GA pilots. Good discipline still matters, but the system leaves a little more room for correction.
- CAT II: A specialized, lower-visibility operation. You need the right airplane, the right runway, and the right authorization.
- CAT III: The far end of low-visibility precision operations. For many GA pilots, this remains outside realistic day-to-day planning.
CAT II is the bridge category. It's lower than standard ILS operations, but it still demands a clear “land or go around” decision at a defined height.
That bridge concept helps prevent confusion. Pilots sometimes hear “low visibility” and lump CAT II and CAT III together. They aren't the same. CAT II still expects a deliberate decision at minimums. You're not solely riding automation into the runway and hoping the runway appears when it appears.
CAT I vs CAT II vs CAT III A Quick Comparison
The fastest way to understand CAT II is to compare it side by side with the categories around it. That keeps you from treating it like either a routine ILS or a near-zero autoland operation.
ILS Approach Categories Compared
| Category | Minimum Decision Height (DH) | Minimum Runway Visual Range (RVR) |
|---|---|---|
| CAT I | 200 feet | 1,800 feet or 550 meters |
| CAT II | Lower than 200 feet but not lower than 100 feet | At least 1,200 feet |
| CAT III | Lower than CAT II | Lower than CAT II |
What those numbers mean in the real world
CAT I is what most instrument pilots build their scan, briefing habits, and missed-approach discipline around. You intercept, stabilize, descend on precise lateral and vertical guidance, and make a decision at a height that still gives you a bit more visual transition time.
CAT II moves that decision lower. That changes the workload profile. The airplane must remain more precisely coupled to the approach path, and the pilot has to be sharper about system status, runway lighting status, and exact minimums.
CAT III goes further still. For a general aviation pilot, the useful point isn't to memorize every subcategory. It's to recognize that CAT III typically involves operations heavily dependent on automation and highly specialized infrastructure.
A good rule of thumb is this:
- CAT I is common
- CAT II is selective
- CAT III is highly specialized
That framing keeps your planning honest. If you're trying to become CAT II capable, you are not just “getting better at ILS approaches.” You're moving into a narrower regulatory lane with more prerequisites and less tolerance for error.
Aircraft and Airport Equipment Requirements
You can brief a CAT II perfectly, fly a clean intercept, and still be unable to continue because one missing piece turns the whole operation back into something above your authorization. That is the mindset shift. For a general aviation pilot working toward CAT II capability, this is no longer just about flying skill. It is about proving that the airplane, the runway, and the supporting systems all match the lower minimums.

What the airplane must bring
A standard IFR panel that handles a normal ILS well is not enough for CAT II. The airplane has to hold tighter tolerances closer to the ground, where small errors stop being small.
One item changes the picture right away: the radio altimeter. Skybrary explains that CAT II uses a decision height below 200 feet and down to 100 feet, and that the procedure requires a radio altimeter because pressure altitude is not precise enough for that last segment of the approach in this precision approach reference.
A barometric altimeter answers, "What altitude am I at based on the current pressure setting?" A radio altimeter answers, "How high am I above the surface right now?" Near the runway, that second answer is the one the system needs.
For the ambitious GA pilot, this is the practical checkpoint: many well-equipped piston and turboprop aircraft can fly excellent coupled ILS approaches, but relatively few are configured, approved, and maintained for CAT II work. Before you spend money on training plans, confirm what your specific aircraft, AFM or AFMS, installed avionics, and autopilot approval allow. A polished panel is not the same thing as CAT II authorization.
Aircraft commonly used for CAT II operations are typically expected to have:
- Dual ILS receivers so one failure does not leave you guessing close to minimums
- A radio altimeter tied to the approved decision-height reference
- A highly accurate coupled autopilot or flight guidance system suitable for the operation
- Clear annunciation and mode awareness so the pilot can confirm what the system is doing at each phase
- Maintenance and inspection status that supports the approval, not just normal IFR dispatch
That last point catches people off guard. CAT II capability works a lot like an ice-protection system. It is not enough for the equipment to be installed. It has to be installed correctly, approved for the operation, and working today.
If you are sorting out which runways and procedures are even worth evaluating for future CAT II planning, a current airport and runway data tool for approach planning can help you screen the field before you get deep into the briefing.
What the airport must provide
The runway has to meet its side of the bargain too. CAT II is a system operation, not an airplane-only upgrade.
In practical terms, the airport needs the right ILS infrastructure, the right lighting, reliable runway visual range reporting, and current low-visibility support procedures. If one of those pieces is out of service, the published CAT II minimums may no longer be available even if your airplane is fully approved.
For a GA pilot, it helps to picture the airport as part of the avionics package. Your glideslope and localizer get you to the runway environment, but the lighting and RVR system are what make that last transition legal and repeatable at lower minimums.
A useful preflight habit is to verify all of these items, not just the weather:
- The runway has CAT II minimums published
- Required approach lighting and runway lighting are operating
- RVR reporting is available and current
- Relevant low-visibility procedures or airport restrictions are in effect as required
- No NOTAM has removed a component that your authorization depends on
That is why a legal CAT II operation can disappear before departure or while you are enroute. The weather may support it, but a failed lighting component, an out-of-service RVR transmissometer, or a change in airport status can raise the minimums or remove the option entirely.
A good cockpit habit is to brief CAT II availability the same way you brief fuel reserves. Do not assume it will still be there when you arrive. Verify it, then verify it again close to the approach.
Pilot Training and Authorization Requirements
You break out at 100 feet above touchdown zone elevation, exactly where a normal instrument approach would leave almost no time to sort out a surprise. At CAT II minimums, the FAA wants proof that your airplane, your procedures, and your training can all handle that moment without hesitation.
For a general aviation pilot, that is the primary shift. CAT II is not an advanced ILS you decide to fly one day. It is a specific authorization tied to the operation, and your instrument rating by itself does not provide it.
Authorization is operational, not personal
In the United States, CAT II authority is issued through OpSpecs, MSpecs, or an LOA. For the ambitious Part 91 pilot, the practical point is straightforward. You need formal approval for the operation, and that approval depends on the aircraft, installed equipment, approved procedures, and pilot qualification working together.
A good comparison is a high-performance airplane with no current annual. The pilot may be fully rated and current, but the flight still is not legal until the whole system is in compliance. CAT II works the same way. Pilot skill matters, but paperwork, equipment status, and approved procedures matter just as much.
That can feel discouraging at first, especially if you are used to adding privileges through ratings alone. In practice, it is a safety filter. Low-visibility flying leaves very little room for improvisation, so the FAA expects a repeatable method, not just good stick-and-rudder confidence.
If you want more examples of procedure-focused IFR reading before formal CAT II work begins, the training articles on PilotGPT's aviation blog are a useful starting point.
What the training is designed to prove
CAT II training is not just harder instrument practice. It is designed to answer a narrower question. Can you fly a highly scripted precision approach, monitor the automation, recognize a problem immediately, and execute the correct response before the airplane runs out of altitude?
That is why the training usually feels more like systems management under pressure than traditional hood work. You are learning to fly with smaller tolerances and sharper decision points.
A typical training program includes:
Ground instruction on legal use and limitations
You learn what approval you need, which equipment must be operative, how minimums are determined, and which failures cancel the approach before it starts or force a missed approach once it is underway.Simulator or approved training device scenarios In these scenarios, the instructor can safely create the failures that matter most. Wrong mode capture, autopilot disconnects, flag warnings, radio altimeter issues, and missed approaches initiated from very low altitude all need to become familiar events, not cockpit surprises.
Repetition of callouts, gates, and missed approach decisions
The goal is to make each action predictable. At CAT II altitudes, there is no spare time for a debate about what to do next.Demonstration to the approving authority or training provider
You are not only showing that you can track localizer and glideslope. You are showing that you can stay inside the approved procedure from intercept to either landing or immediate go-around.
What usually trips up GA pilots
Newly instrument-rated pilots often assume the hard part is hand-flying accurately in low weather. Accuracy matters, but CAT II usually challenges GA pilots in a different way. The primary workload is staying ahead of the airplane while trusting, monitoring, and verifying the automation.
That feels unfamiliar if most of your instrument experience has been built around CAT I minimums and personal judgment. CAT II reduces the amount of judgment left at the bottom. More of the flight must already be decided, briefed, configured, and backed by approved equipment.
A good instructor will keep pressing on the same question: "If this fails now, what is your response?" If your answer takes more than a beat to form, the procedure is not learned well enough yet.
A capable CAT II pilot is trained to go missed just as cleanly as they are trained to continue.
That mindset matters for GA pilots aiming higher than standard IFR. CAT II authorization is less about proving bravery in bad weather and more about proving discipline at the point where options become very small.
Flying the CAT II Approach Procedures and Callouts
Execution is where CAT II stops being a concept and becomes cockpit discipline. The steps themselves won't feel alien to an instrument pilot, but the tolerance for slop is much smaller.

Before the approach starts
A good CAT II starts long before glideslope intercept. By the time you're turning inbound, the briefing should already have answered every question that matters.
Your briefing should cover at least these items:
- Approach authorization: Confirm you, the airplane, and the operation are approved for CAT II.
- Runway status: Verify the runway supports CAT II and that the required low-visibility setup is in effect.
- Minimums source: Confirm the decision height tied to the radio altimeter, not a vague memory of a chart note.
- Automation plan: Know which modes should arm, capture, and remain engaged.
- Missed approach trigger: Decide in advance what will cause an immediate go-around.
A sample mental script might sound like this:
CAT II ILS runway X. Radio altimeter minimums set. Required lighting and RVR confirmed. Coupled approach planned. Any unstable condition, mode anomaly, or lack of required visual reference at minimums results in immediate go-around.
That sounds simple because it should. Complex briefings fail under stress.
From glideslope intercept to decision height
Once established, your job is not to admire how smooth the automation looks. Your job is to monitor it like a hawk.
Useful callouts, whether spoken aloud in single-pilot operations or verbalized in a crew environment, often include:
- “Localizer alive” and “Glideslope alive”
- “Approach mode armed” and later “Approach mode captured”
- “1000 feet, stabilized”
- “500 feet, stabilized”
- “Approaching minimums”
- “Minimums”
The point of these calls isn't ceremony. They force you to check whether the airplane is doing what you think it's doing. In low visibility, mode confusion can be just as dangerous as poor stick-and-rudder technique.
Here's a good moment to watch a visual example of the workload and timing involved:
At minimums
At decision height, the moment is binary. Either the required visual references are there and the approach remains stable, or you go around.
That decision should sound crisp:
- “Runway in sight, landing”
- “No contact, go-around”
There shouldn't be a pause for negotiation. There also shouldn't be a gradual drift below minimums while you “take a peek.” If the runway picture isn't what the procedure requires, the missed approach begins immediately.
Three mistakes show up again and again in practice:
- Chasing the airplane late: If the approach isn't stable earlier, minimums arrive too fast for recovery.
- Trusting automation without monitoring: Coupled doesn't mean self-managing.
- Hesitating at decision height: Indecision below low minimums burns up the little margin you have left.
CAT II rewards pilots who decide early, configure early, and think ahead of the airplane. It punishes everyone else.
Common Pitfalls and How to Avoid Them
The danger in CAT II usually isn't one giant blunder. It's a stack of smaller errors that would be survivable in a less demanding approach. Here, they line up at exactly the wrong time.

The traps that catch pilots
One common trap is press-on-itis. The destination is close, the airplane is technically capable, and the pilot starts mentally searching for reasons to continue despite an equipment issue, missing runway component, or a briefing gap. CAT II doesn't tolerate that mindset well.
Another is automation complacency. Pilots can become so used to a coupled approach that an autopilot disconnect or mode error feels shocking rather than manageable. The airplane hasn't changed. The pilot's readiness has.
The third big trap is minimums confusion. A pilot who is used to barometric callouts may mentally mix that habit with a CAT II procedure that depends on radio-altimeter-based decision height. That's the sort of mismatch that can produce a late go-around or an unauthorized continuation below minimums.
Simple countermeasures that work
The best defenses are boring, specific, and repeatable:
- Use a hard legality gate: If any required approval, equipment item, or runway support element is missing, stop there. No debate.
- Brief the missed approach like you expect to fly it: That keeps the go-around from feeling like failure.
- Say the key callouts out loud: Single-pilot doesn't mean silent-pilot.
- Practice automation dropouts: If the system quits, your hands and brain shouldn't need a warm-up period.
- Separate baro thinking from RA thinking: Put the correct minimums source at the center of the briefing.
For ongoing decision-making discipline and broader personal minimums work, material focused on pilot safety habits can help reinforce the mindset that CAT II requires.
Low-visibility proficiency is really decision proficiency. The airplane can only execute the plan you built before the workload peaked.
A CAT II approach is achievable for a dedicated general aviation pilot. But it only becomes useful when you treat it as a complete operating system, not just a lower set of numbers on an approach plate.
If you want a cockpit tool that supports disciplined flying without adding internet dependence, PilotGPT is built for exactly that environment. It runs offline on your phone or tablet, helps reduce workload during high-task phases of flight, and grounds answers in authoritative aircraft and FAA documents so you can retrieve procedures, airport data, charts, and checklists quickly when it matters most.