Operating in different airspace

This element consolidates the risk-management side of airspace operations: who's flying, what airplane and equipment, what airspace structure and weather, what's pressuring the call, and how each of those plays out in unfamiliar Class B or near an active SUA. The PAVE framework from §91.103 preflight action is the same; the airspace dimension is what gives it teeth here.

Three filters in order: regulatory minimums, personal minimums, PAVE applied to the airspace. Pass all three with no external pressure driving the call → go. Otherwise modify (different time, different route, different altitude, different airspace) or no-go. There is always a third option besides "press on or scrub": route around.

Personal minimums for unfamiliar airspace

Pilot-imposed limits, set tighter than regulatory minimums. Airspace minimums should be tighter when the route crosses unfamiliar territory because workload and surprise both spike when you don't already know the local flow.

Category	Familiar local Class D	Routine XC through Class B/C	Unfamiliar Class B or SUA-heavy
Visibility SM	3	5	7
Ceiling AGL	1,500	3,000	4,000
Bravo/Charlie transit recency	n/a	90 days	30 days
Active SUA along route	OK with ATC	confirmed cold	routed around
TFR margin (lateral)	regulatory	3 NM	5 NM
Schedule pressure	low ok	none	none

Set them in writing before the flight, calibrated to the airspace mix, and don't adjust them under pressure. The point isn't the specific number — it's that you have a number, it's not the regulatory floor, and it factors in unfamiliarity.

Pre-flight airspace check

Three filters in order. The structure mirrors the cross-country planning check but with airspace specifics.

Regulatory minimums

The floor is set by regulation: weather minimums for the airspace per §91.155-class-c-d-e, equipment requirements per §91.215 and §91.225, and the broad preflight-information rule under §91.103 requiring that the pilot become familiar with "all available information" — which for an airspace-crossing flight means current sectional, Chart Supplement SUA data, and NOTAMs.

Personal minimums sit above the regulatory floor (above).

PAVE applied to airspace — four letters, each with airspace-specific content:

• P — Pilot. Currency and proficiency for the airspace specifically. Class B requires PPL minimum and explicit clearance handling; recent Bravo transitions matter. SUA areas require active-status assessment ability. MOA areas require sustained scan during high-speed military traffic. Have I flown THIS airspace mix recently? IMSAFE for the full flight duration including the post-landing radio handoffs at the destination.
• A — Aircraft. Equipped for the airspace. Mode C transponder and ADS-B Out for Class A, B, C, and the Mode C veil; current charts (sectional or EFB cycle current); EFB with TFR overlay if I'm relying on it for TFR awareness. Backup paper sectional in case the EFB fails.
• V — enVironment. Airspace structure along the entire route, not just departure. SUA active status per Chart Supplement and current NOTAMs. TFR overlay checked at planning AND re-checked before departure. Weather impact on workload — Class B workload spikes when ceilings are low; Class C is workable in marginal but adds task load.
• E — External pressures. Am I rushing through unfamiliar Class B because I'm late? Stretching personal mins to penetrate marginal weather inside the Mode C veil because the destination is "just past it"? Accepting a Bravo clearance I'm not comfortable with because the controller is busy and I don't want to bother them? Name pressures out loud — speaking them aloud reduces their power.

Decide. Pass all three filters AND no external pressure is driving the call → go. Any filter fails or pressure is the deciding factor → modify (different route around the Bravo, different time avoiding TFR active hours, different altitude staying below complex shelves) or no-go.

Inadvertent entry and recovery

Inadvertent entry happens to capable pilots. The recovery determines whether it's a learning experience or an enforcement action.

Five-step recovery sequence

1. Turn away immediately on the most direct exit heading. Don't continue while figuring out what to do — the airspace bust is active until you're outside the boundary.
2. Contact the controlling facility on the published frequency. Phrasing example: "Phoenix Approach, Cessna 12345, I believe I may have entered Class Bravo without clearance, exiting on heading 270, request advisory." The "I believe I may have" framing is intentionally conservative — admit the situation, don't speculate on cause or argue.
3. Comply with vectors or instructions ATC provides. They'll typically clear you out and may assign a discrete squawk for tracking.
4. File an ASRS report (NASA Form ARC 277B) within 10 days. Under the ASRS program, an inadvertent violation report typically provides immunity from many enforcement actions when the violation wasn't intentional, didn't involve a criminal offense, and didn't involve an accident.
5. Debrief honestly — what went wrong, what would prevent it next time, what should change in the preflight planning process.

What NOT to do

• Continue toward the destination through the airspace because "I'm almost out."
• Deny or argue with the controller.
• Squawk 1200 to "hide" the track — ATC already has you on radar.
• Skip the ASRS report because filing feels like admitting fault. The opposite is true: filing protects you.

The PIC's emergency authority under 14 CFR 91.3(b) allows deviation from any rule in Part 91 to the extent required to meet an emergency. Inadvertent airspace entry rarely rises to "emergency" — most are recoverable with normal-procedure exit. But if you're inside a Class B without clearance AND IFR conditions develop, declaring an emergency under 91.3 unlocks IFR services and protective handling. Save the declaration for actual emergencies; for inadvertent VFR entry into controlled airspace, the normal recovery sequence is usually sufficient.

External pressures around airspace decisions

Plan-continuation bias in airspace is subtler than in weather but just as dangerous. The pattern: pilot files a route through busy Class B because it's shorter, encounters higher-than-expected workload, but continues because "I'm already in it." The honest response when workload spikes is to request an exit ("Approach, Cessna 12345, request exit of the Class Bravo, will route around") — which is always grantable and removes the workload.

Three pressures specific to airspace decisions

• Avoid-the-controller pressure. "I don't want to bother Approach, they sound busy." This pressure pushes the pilot to skip flight following, decline help when offered, or accept a vague clearance rather than ask for clarification. ATC workload management is the controller's job — make the request; if they can't, they'll say so. "Unable" is a legal answer for them too.
• Direct-route pressure. "Going around the Bravo adds 15 minutes." Fifteen minutes of routine VFR around a Bravo is almost always lower workload and lower risk than the same fifteen minutes spent inside an unfamiliar Bravo with degraded weather. The shorter route isn't the safer route.
• TFR-NOTAM laziness. "I checked NOTAMs this morning, that should be good." TFRs activate dynamically. The pilot who only checks at original departure misses TFRs that activated between morning and a mid-day takeoff. Make NOTAM check a checklist item at every preflight, not a once-a-day task.

Three protections

• Name pressures out loud during PAVE. "I have a meeting tomorrow but the airspace doesn't care about my meeting." Speaking pressures aloud reduces their power.
• Pre-set decision points in writing. "If the Bravo workload exceeds my capacity within 5 minutes of entry, I request an exit and route around." Then act mechanically when the trigger fires.
• Treat 'route around' as the default option, not as a concession. The three real options are route around, request an exit if already in, or scrub. Pressing on through workload-saturated airspace is not on the safe-options list.

Worked example:

• Bravo-saturated arrival, real-time exit. Pilot on flight following en route to a satellite airport near a major Class B. Pre-flight plan was to overfly the Bravo at 8,500 MSL above the 6,000 ft top of the outer shelf. En route, Approach assigns a vector that brings the aircraft over the inner core where the ceiling is only 4,500 MSL — pilot didn't realize this sector had a lower top, now needs clearance to be at 8,500 over that sector. Pilot recognizes the gap immediately and transmits: "Approach, Cessna 12345, am I cleared into the Bravo? My understanding was the top here is 4,500." Approach confirms: "Cessna 12345, you're cleared into the Class Bravo at 8,500, maintain heading." Now legal. Alternative had the pilot not asked: continued at 8,500 over the inner core without explicit clearance — Bravo bust. The recovery here was preventive, not after-the-fact: the pilot asked when uncertain, the controller filled the gap. The honest question is always cheaper than the recovery from the violation.