MBI 08-05 - Release Requests and Rolling Calls

Controllers must read

Moderators: Manuel Manigault, Justin Martin

MBI 08-05 - Release Requests and Rolling Calls

Postby Jared Shure » Sat Mar 22, 2008 10:17 am

MBI 08-05 - Release Requests and Rolling Calls

The departure controller needs to approve all aircraft to depart prior to the aircraft commencing their takeoff roll. This can be accomplished a few ways. Unless requested by the departure controller, the tower shall have a "blanket release" and aircraft may depart without a specific request from the departure controller. Tower must provide the departure controller with a rolling call (see below). The departure controller may suspend the blanket release and tower must request releases (see below) for every departure. Release requests should be used if the departure sector is busy, extended in trail spacing is required, etc. This allows for the departure controller to control the departure rates.

Note: All references to the departure controller refer to the controller covering the departure sector for the specific airport. This may be DEP or APP for that airport, another DEP or APP, or CTR.

Use the text override or chatbox. Voice override may be used, but ask the controller you are overriding if their override even works, because some personal networks may not be set up properly and G/G voice may cause other problems.

Rolling Calls:
Shall be made no sooner than when the aircraft commences departure roll and no later than the aircraft reaching the departure end of the runway.
Include the following information:
i. Call sign.
ii. Departure runway.
iii. Heading if non-standard or additional information/restrictions as needed/required.
iv. IFR departure fix, initial route, or name of local airport/destination, and the term VFR if appropriate.

Eventually we will push departure strips to accomplish this

Release Requests:
Shall be made up to five (5) minutes prior to aircraft beginning their departure roll.
i. Call sign.
ii. Departure runway.
iii. Heading if non-standard or additional information/restrictions as needed/required.
iv. IFR departure fix, initial route, or name of local airport/destination, and the term VFR if appropriate.
v. Estimated Takeoff Time and Departure Sequence

Note about text override:
To use text override type: .msg [callsign] *** [Message] <enter>
or, if a chatbox is already open, type: *** [message] <enter>
The *** is what drives the text override system.
User avatar
Jared Shure
Past Chief/ATM
 
Posts: 413
Joined: Tue Jun 03, 2003 5:54 pm
Location: New Haven, CT

Return to Mandatory Briefing Items

Who is online

Users browsing this forum: No registered users and 1 guest