dcsimg
This website is not affiliated with the U.S. government or military.

RECONNAISSANCE SCHEDULING REPORT [RECON 3]

Use (1) to provide selected and specific data on proposed reconnaissance mission schedules, (2) to make changes to approved schedules, and (3) to inform of CINC/unit intention to fly specific reconnaissance missions. Reference: FM 34-2-1 and FM 101-5.

LINE 1 -- DATE AND TIME______________________________(DTG)

LINE 2 -- UNIT________________________________________(Unit Making Report)

LINE 3 -- TRANSACTION_______________________________(SCHEDULE, ADD, CANCEL, CHANGE, DELAY, INDEFINITE DELAY, or RESCHEDULE)

LINE 4 -- PERIOD______________________________________(Mission Schedule Month and Year)

LINE 5 -- REASON_____________________________________(Reason for Mission)

LINE 6 -- MISSION NAME ______________________________(Mission Nickname)

LINE 7 - MISSION DATA FOLLOWS______________________(Alerts receiver that the next eleven lines contain Mission Data. When sending data for more than one mission, state the number of the mission being sent.)

EXAMPLE: MISSION DATA FOLLOWS; FIRST MISSION

LINE 8 -- MISSION_____________________________________(Mission Number)

LINE 9 -- TRACK ______________________________________(Mission Track Number)

LINE 10 -- NUMBER TYPE ______________________________(Count and Type of Aircraft)

LINE 11 -- PURPOSE ___________________________________(Primary and Secondary Codes)

LINE 12 -- TAKEOFF___________________________________(Estimated Departure DTG Zulu)

LINE 13 -- BASE_______________________________________(Departure Base ICAO Code)

LINE 14 -- LANDING___________________________________(Estimated Arrival DTG Zulu)

LINE 15 -- BASE_______________________________________(Recovery Base ICAO Code)

LINE 16 -- ASSESSMENT _______________________________(Mission Assessment Code)

LINE 17 -- CONTINGENCY______________________________(C if a Contingency Mission)

LINE 18 -- COORDINATED______________________________(C and 1 Through 9)

**Repeat lines 7 through 18 to report multiple missions. Assign sequential line numbers to succeeding iterations; for example, first iteration 7 through 18; second iteration 7a through 18a; third iteration 7b through 18b; and so on.

LINE 19 -- TRACK OPTION DATA FOLLOWS______________(Alerts receiver that the next three lines contain Track Option Data. When sending data for more than one mission, state the number of the mission being sent.)

EXAMPLE: TRACK OPTION DATA FOLLOWS; FIRST TRACK

LINE 20 -- MISSION____________________________________(Mission Number of Multitrack Mission Being Scheduled)

LINE 21 -- OPTIONS____________________________________(Optional Track Numbers and Mission Assessment Codes)

**Repeat lines 19 through 21 to report multiple multitrack missions. Assign sequential line numbers to succeeding iterations; for example, first iteration 19 through 21; second iteration 19a through 21a; third iteration, 19b through 21b; and so on.

LINE 22 -- COORDINATED MISSION DATA FOLLOWS _____(Alerts receiver that the next three lines contain Coordinated Mission Data. If you are sending data for more than one mission, state the number of the mission being sent.)

EXAMPLE: COORDINATED MISSION DATA FOLLOWS; FIRST MISSION

LINE 23 -- MISSION ___________________________________(Mission Number of the Coordinated Mission Being Scheduled)

LINE 24 -- WITH_______________________________________(Up to 6 Coordinated Mission Numbers)

**Repeat lines 22 through 24 to report multiple multitrack missions. Assign sequential line numbers to succeeding iterations; for example, first iteration 22 through 24; second iteration 22a through 24a; third iteration 22b through 24b; and so on.

LINE 25 -- SPECIAL DATA______________________________(Enter data that does not belong in another line.)

LINE 26 -- NARRATIVE_________________________________(Free Text for Additional Information Required for Clarification of Report)

LINE 27 -- AUTHENTICATION___________________________(Report Authentication)