Washington Dulles
A major international gateway with dedicated general aviation FBO facilities, considered for Washington, Northern Virginia, diplomatic, and global missions.
Submit for Consideration
Private Aviation Locations Washington, D.C.
Access must satisfy the mission and the environment.
DFI governs Washington private aviation around airport suitability, security requirements, airspace procedures, ground movement, and continuity responsibility.
Security • Authorization • Gateway Selection • Continuity
01
The Washington Mandate
Access is conditional by design
Washington requires more than aircraft and airport availability.
The Washington metropolitan area operates within security sensitive airspace. The Special Flight Rules Area, Flight Restricted Zone, temporary restrictions, airport procedures, and authorization requirements can affect how a mission is planned and whether a preferred gateway is available.
DFI evaluates the aircraft, operator, airport, security and procedural requirements, destination geography, timing, ground movement, and credible alternatives before access is confirmed. Current governmental instructions and operating approvals always govern the mission.
Gateway decision discipline
Dulles anchors access. Regional gateways serve different responsibilities.
Manassas Regional
Virginia’s largest general aviation airport and a Washington regional gateway considered for Northern Virginia and suitable domestic missions.
Leesburg Executive
A Dulles reliever on the boundary of the Washington Special Flight Rules Area, considered for Loudoun County and suitable business aviation missions.
Restricted and Mission Specific Gateways
Reagan National general aviation requires applicable TSA authorization. BWI and other regional airports may be evaluated when security, geography, aircraft, international, or recovery requirements justify them.
02
Security and Ground Coordination
Authorization must exist before access is assumed
Washington movement is governed before departure.
Before Confirmation
Eligibility and Procedure
Before Departure
Clearance and Documentation
At Arrival
FBO and Security
On the Ground
Protected Transfer
Flight permissions, crew and aircraft requirements, passenger documentation, FBO procedures, vehicle access, security posture, luggage, destination entrance, and timing must be confirmed for the specific mission. Proximity to Washington does not create authorization to operate within restricted airspace.
The capital region is not one destination
Capitol Hill, Downtown, Northern Virginia, and Maryland require different ground strategies.
Bridge and highway conditions, security perimeters, motorcade activity, government schedules, major events, and destination protocols can change the value of an airport after landing.
01
Mission, party, and destination profile
02
Aircraft, operator, and runway suitability
03
Security eligibility and current procedures
04
Airport, FBO, and handling coordination
05
Vehicle, security, and luggage plan
06
Restrictions, events, and traffic exposure
07
Alternate gateway decision triggers
08
Recovery authority and escalation
03
Continuity Planning
When authorization or conditions change
The alternate must remain compliant and operationally suitable.
A credible Washington continuity plan identifies which gateway remains available, what procedures apply, how aircraft and crew are affected, where ground transportation must reposition, and which commitments must continue. DFI prepares the decision architecture before urgency reduces the options.
In Washington, prepared access means knowing what is permitted before determining what is preferred.
Private consideration
Define the Washington responsibility.
Prepare compliant access around it.
Submit the mission for private consideration. DFI will evaluate the aircraft, gateway, applicable requirements, ground movement, timing, and continuity responsibilities before access is confirmed.
Submit for Consideration