Radar Bible
(Study purpose only, some of these procedures may have changed and or are worng)
I. VFR calls up requesting flight following
1.If R-side writes the ACID, Type/Suffix and Route down on a blank strip, great. If I am not busy, than I should write it down
2.Take info and enter a VP msg
1.VP
Acft type/Suffix_Route_AcftCallsign
II. VFR calls up with IFR flight plan on File
1.DM CID (Check Dep list for)
III. A/C Flashing Data or Mism
1.Call transfering controller
1.(facility) Jan Lo, Pos Verifaction
2.(ACID) Verify Position
3.(ACID) Radar Contact
2.If position is verified
3.Start track
1.Track_CID
4.Tell r-side
1.(ACID) Position Verfied
5.Tell Sup on Mism only
1.Received a MISM from (facility),(ACID) is position verified
IV. Receiving a manual handoff w/ a flight plan
1.Transferring Facility will call and say
1.Handoff w/a Flightplan
2.“go ahead with handoff”
2.Write down beacon, ACID Alt
1.“(ACID) radar contact”
2.“Stand by with flight plan”
3.Tell R-side
1.“I took a handoff from (Facility), Location, Beacon, ACID & Alt”
4.Determine FRD & Time & write on strip
1.“proceed w/ flight plan”
5.Enter FP as soon as time permits
V. Passing Manual Flight Plan
1.contact receiving facility & execute a handoff
VI. A/C calls in requesting higher, lower or reroute
1.Take note of ACID & request specfiics
2.look to see where the A/C is;
1.if over another sector, request specifc control from that sector
2.if over Apch and request lower, give lowest availble alt and PO to Apch
3.if leacving Apch wanting higher, trail plane and excute
4.if on J4 in MLU airspace get CTL from MLU
1.Ref. PO to 67 for new alt only, (PO was initally made by MLU)
3.If wanting higher or lower trial plan alt, you may have to miss traffic
4.tell R-side specifics
1.Control from who and what is to be done
VII. Any dept from Vks or Gwo
1.Check for any inbounds on y0our strips
2.check for any overflights & Alts
3.check for inbounds to other airports along route that will cause a conflict
1.tell r-side and ensure separation
4.If there is any inbound to same airport more then 20 miles away
1.tell r-side “Keep your (airport) arrival above (alt), I have a (airport) depature to get off to (alt)”
****If KVKS VKS DORTS MLU,
any mlu depts must be above 050
****Watch out for 030 & 040 overflight departing from GLH & STF
**** VKS Navaid Limitions (No Direct SQS) If you change route or add VKSRB youi must

“Verify this …”
****VKS Navaid limitions
VKS MLU (PO or Appraq to MLU APCH and MLU LO)
VKS HEZ (Appraq with Poe low)
VKS BLE (PO 67 direct SQS)
VKS JAN (If you do not turn direct SQS you will need a PO or Apprq to Jan Lo, if you do you may need a PO to JAN APCH and 67)
VKS MCB (Poss PO to POE lo and Apprq with HMU lo)
****GWO depatures can only be cleared to XXX alt if a 0M8 has been released you must get a report leaving of 031
**** Unrestricted climb out of GWO, Check all ALTs of SQS overflights and ALT of 0M8
VIII. 0M8 depts
1.Issue EDC time
2.Call 67
1.Apreq, block 040 and below for 0M8 departures”
1.If unable reroute ^JAN and use “Verify this Clear …”
3.If Approved- Check for inbounds, Alts & GWO departures/inbounds/overflights
4.Issue Full Clear
1.Tell R-side Dept. Climbing to 040 or Alt Available
5.Track //0M8 Callsign
6.Int 040 (Fake beacon code, use code from the Track msg)
7.Once acft has departed DM CID (Use real beacon code)
1.If you have a block with 67
1.PVD CID, PO north of barley callsign, climbing Alt, direct SQS
2.Cancel Depature Block
3.tell R-side 67 approved a PO on C/S climbing to Alt direct SQS
4.Mark you strips pull the strip if R contact and strip marking is complete
2.No block with 67
1.tell R-Side direct SQS when able
2.PO 67 or Jan Apch may be ness.
3.If you forget about the direct SQS PO or Apprq with Jan will be ness.
XI Traffic climbing high through another sector (who ref. traffic)
1.Ask r-side
1.“can we climb (PO Acft) above (Traffic A/C)?”
1.If yes traffic observed
(Study purpose only, some of these procedures may have changed and or are worng)
I. VFR calls up requesting flight following
1.If R-side writes the ACID, Type/Suffix and Route down on a blank strip, great. If I am not busy, than I should write it down
2.Take info and enter a VP msg
1.VP
II. VFR calls up with IFR flight plan on File
1.DM CID (Check Dep list for)
III. A/C Flashing Data or Mism
1.Call transfering controller
1.(facility) Jan Lo, Pos Verifaction
2.(ACID) Verify Position
3.(ACID) Radar Contact
2.If position is verified
3.Start track
1.Track_CID
4.Tell r-side
1.(ACID) Position Verfied
5.Tell Sup on Mism only
1.Received a MISM from (facility),(ACID) is position verified
IV. Receiving a manual handoff w/ a flight plan
1.Transferring Facility will call and say
1.Handoff w/a Flightplan
2.“go ahead with handoff”
2.Write down beacon, ACID Alt
1.“(ACID) radar contact”
2.“Stand by with flight plan”
3.Tell R-side
1.“I took a handoff from (Facility), Location, Beacon, ACID & Alt”
4.Determine FRD & Time & write on strip
1.“proceed w/ flight plan”
5.Enter FP as soon as time permits
V. Passing Manual Flight Plan
1.contact receiving facility & execute a handoff
VI. A/C calls in requesting higher, lower or reroute
1.Take note of ACID & request specfiics
2.look to see where the A/C is;
1.if over another sector, request specifc control from that sector
2.if over Apch and request lower, give lowest availble alt and PO to Apch
3.if leacving Apch wanting higher, trail plane and excute
4.if on J4 in MLU airspace get CTL from MLU
1.Ref. PO to 67 for new alt only, (PO was initally made by MLU)
3.If wanting higher or lower trial plan alt, you may have to miss traffic
4.tell R-side specifics
1.Control from who and what is to be done
VII. Any dept from Vks or Gwo
1.Check for any inbounds on y0our strips
2.check for any overflights & Alts
3.check for inbounds to other airports along route that will cause a conflict
1.tell r-side and ensure separation
4.If there is any inbound to same airport more then 20 miles away
1.tell r-side “Keep your (airport) arrival above (alt), I have a (airport) depature to get off to (alt)”
****If KVKS VKS DORTS MLU,
****Watch out for 030 & 040 overflight departing from GLH & STF
**** VKS Navaid Limitions (No Direct SQS) If you change route or add VKSRB youi must
****VKS Navaid limitions
VKS MLU (PO or Appraq to MLU APCH and MLU LO)
VKS HEZ (Appraq with Poe low)
VKS BLE (PO 67 direct SQS)
VKS JAN (If you do not turn direct SQS you will need a PO or Apprq to Jan Lo, if you do you may need a PO to JAN APCH and 67)
VKS MCB (Poss PO to POE lo and Apprq with HMU lo)
****GWO depatures can only be cleared to XXX alt if a 0M8 has been released you must get a report leaving of 031
**** Unrestricted climb out of GWO, Check all ALTs of SQS overflights and ALT of 0M8
VIII. 0M8 depts
1.Issue EDC time
2.Call 67
1.Apreq, block 040 and below for 0M8 departures”
1.If unable reroute ^JAN and use “Verify this Clear …”
3.If Approved- Check for inbounds, Alts & GWO departures/inbounds/overflights
4.Issue Full Clear
1.Tell R-side Dept. Climbing to 040 or Alt Available
5.Track //0M8 Callsign
6.Int 040 (Fake beacon code, use code from the Track msg)
7.Once acft has departed DM CID (Use real beacon code)
1.If you have a block with 67
1.PVD CID, PO north of barley callsign, climbing Alt, direct SQS
2.Cancel Depature Block
3.tell R-side 67 approved a PO on C/S climbing to Alt direct SQS
4.Mark you strips pull the strip if R contact and strip marking is complete
2.No block with 67
1.tell R-Side direct SQS when able
2.PO 67 or Jan Apch may be ness.
3.If you forget about the direct SQS PO or Apprq with Jan will be ness.
XI Traffic climbing high through another sector (who ref. traffic)
1.Ask r-side
1.“can we climb (PO Acft) above (Traffic A/C)?”
1.If yes traffic observed