ART-2025 • Module 1 • Inter-Unit Coordination Console

TWR ↔ SMC TWR • SMC

#	Coordination Item
1	IAF start-up in operational area: release from IAF side to TWR for taxi. (IAF helipads coincide with PTT.) SMC issues taxi only in coordination with TWR.
2	TWR informs SMC about expected taxiway for ARR vacation; and alternate vacation plans as required.
3	Departure sequence / spacing is normally TWR ↔ APP. SMC must still tell TWR if SMC already coordinated spacing with APP (so Tower knows what's agreed).
4	Repositioning between Apron II ↔ Apron I (and similar stand transfers) is coordinated by SMC with TWR under VFR taxi instructions.

Summary: surface movement is not isolated — Tower and Ground must continuously share taxi plans, runway exit/vacation info, and sequence expectations.

TWR/SMC ↔ APP/ASR TWR • SMC • APP/ASR

TWR → APP / ASR	APP / ASR → TWR / SMC
• Go-around / Missed approach • Unreported / overdue aircraft • Departure sequence • Runway in use, QNH, RWY closure / u/s • Training / tests in progress • Anticipated ARR delay due VVIP • Significant weather / windshear / bird activity • Need extra time for backtrack • Essential local traffic on/near RWY • ARR vacating via TWY “G” for spacing	• Approval for VFR start-up • Approvals & ATC clearance (as applicable) for surface movement / departure

Idea: Tower/Ground keeps Approach informed about what’s happening on the runway. Approach clears start-ups and feeds Tower/Ground with anything that affects them.

ACC-D ↔ SMC / TWR ACC-D • SMC • TWR

#	Coordination Item
1	At start-up, SMC informs ACC-D of requested cruising level and updates FDD as applicable.
2	On request, SMC gives ACC-D the EDT (estimated departure time) and informs any revision > 3 min.
3	SMC tells ACC-D about helicopter departures from Guwahati to FIR destinations.
4	ACC-D passes ETA revisions / cancellations to SMC / TWR.
5	SMC/TWR → ACC-D: sudden VIS / RVR change, navaid u/s, runway-in-use change, etc.
6	ACC-D → SMC/TWR: any restrictions to departures, navaids u/s, airport closures, etc.

Key link: ACC-D needs current departure intentions and surface status. Tower/Ground needs ACC-D’s restrictions, slot impact, etc.

APP ↔ ACC (Area & Approach) APP • ACC

APP → ACC (inform):	ACC / RSR → APP (inform):
1) Availability of lower levels on ATS routes 2) EAT & avg inter-arrival interval; EAT revision ≥ 5 min 3) Overdue / unreported aircraft info 4) Deviations / restrictions due to traffic 5) Missed approaches 6) Relevant VFR / SVFR departures	1) Arrival sequence 2) Emergencies / priority landings inbound 3) Departures to be released on a specific track / heading / level 4) Procedural training in progress 5) Inbounds deviating from normal routes (vectors / weather) 6) Flights ≤ FL140 that are likely to enter / transit APP; pass that data

This is the main “approach vs area control” pipeline: APP gives arrival flow info upwards, ACC/RSR gives inbound picture and any special handling downwards.

RSR ↔ ACC-D RSR • ACC-D

#	Coordination Item
1	ACC-D informs RSR (Radar / Surveillance): requested level availability & traffic info after SMC start-up.
2	Pre-departure level and ATC clearance for out-stations in Guwahati ACC/FIC is coordinated with RSR.
3	RSR helps with climb / descent for arrivals & departures in coordination with ACC-D.
4	RSR checks estimates and reports back to ACC-D if needed.
5	ACC-D briefs RSR about: • Hashimara activation • Tezpur fighter flying • Temporary airspace activity (RPA ops, balloons, etc.)
6	RSR updates ACC-D with significant movement / control data and position reports.

RSR is the radar picture. ACC-D is planning / enroute clearance. They must constantly sync about restrictions, special activity, and real aircraft positions.

ACC-A ↔ ACC-D ACC-A • ACC-D

#	Coordination Item
1	ACC-A coordinates with ACC-D about pre-departure levels and ATC clearance requests from civil / defence units / adjacent ACC / FICs.
2	ACC-D can task ACC-A to pass estimates, revisions, level changes and significant data to the concerned units.
3	ACC-A coordinates with APP/ASR for traffic inside APP airspace and relays that operational picture to ACC-D.
4	ACC-A relays info on Hashimara / Tezpur activity to ACC-D and supports ACC-D in maintaining situational awareness.

ACC-A is basically helping ACC-D manage all the pre-coordination load, including military or external ACC/FIC requests.

Safety Measures — Military Activities Hazardous to Civil Ops NOTAM • SSIs • TLIs

#	Procedure / Measure
1	Military / hazardous activity should be intimated to ATC at least 7 days in advance. ATC plots the area and issues SSIs / TLIs / circulars so that all controllers are aware.
2	Publish required NOTAMs to all concerned units.

Purpose: make sure civil traffic is warned early and controllers have written local instructions before the activity even starts.

Coordination with Military Authorities IAF • Army • MLC • RPA

#	Rule / Action
1	Weather deviation towards restricted / IAF airspace: inform MLC. Instruct aircraft to contact the appropriate IAF ATC before crossing into their airspace.
2	Direct routing on pilot request: coordinate with MLC first, include reason for request; obtain approval prior to issuing.
3	Conflict resolution: if using restricted / IAF airspace will solve a conflict, coordinate via MLC or directly with IAF ATC before using it.

RPA Operations

LOA between Guwahati Area and Military (IAF / Army) for Remotely Piloted Aircraft (RPA) exists and is held at all ATS Units.

Military coordination is not optional. Civil ATC must get positive approval before allowing civil traffic into restricted blocks.

AAI ↔ Airport Operator (GIAL) LOA • GRF / RCR

#	Agreement / Flow
1	AAI ↔ GIAL is governed by a Letter of Agreement (LOA) on “Communication & Coordination between ATS (AAI) and Airport Operations (GIAL)”.
2	Runway Surface Condition Reporting is as per GRF SOP (GAU/SFT/SOP/10, 22-10-2021) and LOA (25-10-2021); reference ATMC 02/2021.

The purpose is common runway status awareness: friction, contaminants, RCR broadcast, etc.

Airline Operator ↔ ATS Ops Info

#	Expectation / Service
1	ATS considers operator requirements and, when requested, provides information needed for the operator to meet its responsibilities.
2	When requested, ATS forwards relevant messages (including position reports) to the operator or its nominated representative, as practicable.

This is mainly about sharing operational info to the airline when they explicitly ask (slot, delay info, etc.).

Meteorological Unit ↔ ATS Briefing • TWR • Phone

#	Coordination Mode
1	Coordination is effected between ATC and MET units either in-person (TWR / briefing office) or via telephone.

Controllers should know how to quickly reach MET for updated TREND / weather / SIGMET-type info.

AIS ↔ ATS International NOTAM Office (Kolkata)

#	Coordination Mode
1	Coordination between ATC and AIS is through AFTN messages or telephone, including via the International NOTAM Office (Kolkata).

AIS is the pipeline for formal publication. ATC must ensure important status changes are notified in a form AIS can actually publish.