Baltimore-Washington Clearance SOP
Frequency
- VHF - 118.05
Departure Procedures
There are 2 published departures, the SWANN3 and PALEO3. Both departures are PILOT NAV and go to the EAST
All eastbound departures must be on one of the 2 departures if they are PILOT NAV equipped
The PALEO3 departure should be filed as PALEO3.ACY (for the ACY transition) or PALEO.ENO (for the ENO transition) or PALEO.SIE (for the SIE transition)
The SWANN3 departures should be filed as SWANN3.DQO (for the DQO transition) or SWANN3.OOD (for the OOD transition).
All other aircraft will be cleared via radar vectors to their departure
gate
Initial altitude
4,000 for all typesDeparture Gates
Unless coordinated with the departure controller, all aircraft will use one of the following departure gates
| Direction | Gate |
| North | EMI |
| East | SWANN, PALEO |
| South / Southeast | DAILY |
| South / Southwest | HAFNR, FLUKY |
| West | LDN, AML (J149) |
| Northwest | MRB, BUFFR, JERES |
Departure Frequency
- When there is just one Baltimore Departure (BWI_DEP) controller online, the departure frequency for all exits is 128.7.
- When there are two (2) Baltimore Departure (BWI_DEP) controllers online,
the departure frequency is,
- 124.55 for SWANN and PALEO exit gates
- 128.70 for HAFNR, FLUKY, LDN, AML, MRB, BUFFR and JERES exit gates
- For DAILY exits, the departure frequency is determined by the departure
runway
- 124.55 for runways 10, 15R, and 15L
- 128.7 for runways 28, 33L and 33R