PWS Attachment 4 - Installation-Specific sUAS Operations Requirements.pdf

Attachment 4: Installation-Specific sUAS Operations Requirements

Summary Table:

Installation POC sUAS Ops Permitted

CONEMP

Approved

Questionnaire Provided

Key Installation-Specific Restrictions / Limitations

AF Plant #42 Neal "Matt" Fisher -neal.fisher@us.af.mil

- (661)275-9342

YES WITH

RESTRICTIONS

NO YES

400' AGL limit. Site areas are under the operational control of the lessee (contractor) and access to these areas requires coordination with the individual site contractors through the Airfield Manager. Some restrictions on access may apply.

Altus AFB / Clinton Sherman

Troy Bame – troy.bame@us.af.mil

– DSN 866-7804 / (580) 481-7804

YES WITH

RESTRICTIONS

NO YES

200' AGL ceiling; imagery of tail numbers, facades, checkpoints prohibited; ops 0900–0230L Mon– Fri; preferred sunrise–0900 or weekends;

ETP Waiver until CONEMP complete

Arnold AFB Unknown Unknown Unknown NO Unknown

Columbus AFB / Shuqualak AAF

Unknown Unknown NO NO N/A

Dobbins ARB MSgt Christopher Hyde -christopher.hyde@us.af.mil

- (678) 655-4907

YES WITH

RESTRICTIONS

NO YES

400' AGL limit. Entire installation is restricted without specific written approval through FAA, Dobbins Base Operations, Public Affairs, and Security Forces and the Lockheed Martin properties.

Grissom ARB Keith Atkinson – keith.atkinson.4@us.af.mil

- (765) 688-4399

YES WITH

RESTRICTIONS

YES YES

No flights over SE prison; FAA COA may be required; aircraft/building imagery limits; 400' AGL max; restricted during manned ops

Installation POC sUAS Ops Permitted

CONEMP

Approved

Questionnaire Provided

Key Installation-Specific Restrictions / Limitations

JBMDL

Michael Polhemus – michael.polhemus.1@us.af.mil

– (609) 754-3745

YES WITH

RESTRICTIONS

YES YES

No ops in R5001; Navy test coordination required;

no imagery of prisons/checkpoints; restricted to launch/recovery windows

Keesler AFB

Shawn Robertson

– shawn.robertson.2@us.af.mil

- (228) 377-8962 John McDill -john.mcdill.1@us.af.mil

- (228) 377-0138

YES WITH

RESTRICTIONS

NO YES

COA required; 400' AGL limit; ops limited between 0800L and official sunset

Little Rock AFB SSgt Taylr Poley – taylr.poley@us.af.mil

– (501) 987-6668

YES WITH

RESTRICTIONS

YES YES

No flightline ops during wing flying hours;

housing/dorms require 19 SFS approval; camera redirection required; 200' AGL; daytime ops only

Luke AFB / Gila Bend AAF

Awaiting Response NO Awaiting Response

Awaiting Response

Awaiting Response

Minneapolis ARS Ted Trolson – ted.trolson.1@us.af.mil

– DSN 783- 1912

YES WITH

RESTRICTIONS

NO YES

MSP airport coordination may be needed; public affairs oversight; no tail number imagery

Moron AB Unknown Unknown N/A NO EASA UAS Certifications required for contractors, MAJCOM POCs have never worked with Spain before for HN approvals

Pituffik SB

Julie Heiser

– julie.heiser.2@spaceforce.mil

Josh Ludwig

– joshua.ludwig@spaceforce.mil

YES WITH

RESTRICTIONS

NO YES

No ops within 2000 ft of radars/Det- 1; airfield

ATC zone restricted when open; daylight-only ops

Installation POC sUAS Ops Permitted

CONEMP

Approved

Questionnaire Provided

Key Installation-Specific Restrictions / Limitations

Ramstein AB

Derek Brockmann – derek.brockmann@us.af.mil 86AW.sUAS.OSO@us.af.mil

– DSN (314) 478-6972

YES WITH

RESTRICTIONS

YES YES

Use DOZ Map; no flights near aircraft or munitions; 400' AGL max; no tail number/facade/checkpoint imagery

Spangdahlem AB SrA Aaliyah Griggs

YES WITH

RESTRICTIONS

NO YES

400' AGL limit. Restrictions within the flightline area, coordinate with Airfield Manager for guidance and approvals.

Travis AFB Kenny Perkins – kenneth.perkins.1@us.af.mil

– (707) 424-3537

YES WITH

RESTRICTIONS

YES YES

No-fly zones: housing, bunkers, AFOSI, TACAMO;

max 200' AGL (general); 75' AGL on ramp per CONEMP

Vance AFB / Kegelman

Gregory Blakley – gregory.blakley.1@us.af.mil

– DSN 448-6276 / (580) 213-6276

NO N/A NO

Installation designated a "No Drone Zone" by Wing Commander

AF Plant 42

Included Documents:

- Installation Screening Questionnaire

Subject: sUAS Operations for Pavement Inspection - Installation Requirements & Restrictions

Purpose: To gather information regarding sUAS operational requirements and restrictions at your installation in preparation for the upcoming FY25 pavement inspection contract. This information will be used to inform potential contractors/bidders and ensure safe and compliant sUAS operations.

Background: In recent pavement inspection contract solicitations, the Air Force Civil Engineer Center (AFCEC) has received competitive proposals incorporating the use of contractor-owned and operated sUAS platforms to collect downward-facing (nadir) imagery of some or all pavement surfaces (airfields, roads, and parking areas) for distress inventory and Pavement Condition Index (PCI) assessment. Several benefits of this proposed data collection methodology above traditional manual inspection methods include 100% geolocated distress inventory and image capture, which may result in:

• Improved scope definition for airfield preventative and corrective maintenance and repair projects

• Provide for a photographic record of “ground truth” for a given inspection

• Eliminates redundant work for installations in the form of separate project-level surface condition inspections

• Enhanced survey repeatability

In order to ensure that these proposals are fairly considered in upcoming contract solicitations, it is necessary for AFCEC to understand and define installation-specific operational requirements and restrictions so that contractors can tailor their proposals accordingly.

Assumptions:

• The contractor will be using a COTS sUAS platform/sensor payload from the DIU’s "Blue" list located at: https://www.diu.mil/blue-uas-cleared-list.

• The contractor will have completed all necessary external approvals (e.g., COTS exemption, ETP, FAA certifications) prior to requesting installation-specific approvals.

• The contractor will be responsible for implementing and maintaining robust data security measures throughout all phases of the project, including data collection, processing, storage, and transmission. These measures will comply with all applicable DoD and Air Force cybersecurity regulations and policies.

Questionnaire:

Section 1: sUAS Program Point of Contact

1. Does your installation have a designated Installation Project Management Office (IPMO) or sUAS Program Manager responsible for overseeing sUAS operations?

o Yes x☐ No ☐

2. If yes, please provide the following contact information:

o Name: Neal “Matt” Fisher o Title: Airfield Manager o Email Address: neal.fisher@us.af.mil o Phone Number: (661) 275-9342

Section 2: Airspace and Operational Approvals

1. What are the specific steps a contractor must take to obtain approval to operate a sUAS within your installation's airspace? Please provide a detailed explanation or a link to relevant instructions/procedures.

2. Does your installation have an approved CONEMP or guidance document that contractors must utilize?

o Yes ☐ No x

3. If yes, please provide a copy of the CONEMP or guidance document.

4. Is there a certain frequency spectrum the contractor would have to operate under (e.g., 2.4 GHz, 5 GHz, etc.)? Would the contractor be assigned a temporary frequency? Yes, the contractor may be assigned a discrete, however most operations will require the contractor to operate on the control tower primary VHF frequency 123.7.

Section 3: Image Collection Restrictions and Limitations

1. Are there any specific areas on the installation where sUAS flights are strictly prohibited (e.g., near sensitive facilities, critical infrastructure, or ongoing construction projects)?

Please provide a detailed list and/or map. PMD airfield is owned by the DoD and is under the operational jurisdiction of the Air Force. Adjacent areas or sites are leased to aircraft contractors. These sites access the airfield by connecting taxiways. Site areas, ramps, taxiways, buildings, aircraft hangars, etc. are under the operational control of the lessee (contractor) and access to these areas requires coordination with the individual site contractors through the Airfield Manager. Some restrictions to access may apply.

2. Are there any restrictions on capturing imagery of specific assets or areas? Examples include:

o Aircraft tail numbers: Yes x☐ No ☐ o Building facades: Yesx ☐ No ☐ o Security checkpoints: Yes x☐ No ☐ o Other (please specify):

3. Are there any altitude restrictions for sUAS operations on the installation?

o Yes x☐ No ☐

4. If yes, please specify the maximum permitted altitude(s): At or below 400’ AGL

5. Are there any specific time-of-day restrictions for sUAS operations (e.g., prohibited during specific hours, limited to daylight operations only)? Yes, limited to daylight only. Additional earlier restrictions may apply during daylight savings time.

o Yes x☐ No ☐

6. If yes, please specify the permitted operating hours: Varies with time of year

Are there any other unique restrictions, limitations, or considerations related to sUAS operations on your installation that contractors should be aware of? Contractors, to include small UAS operating on plant will coordinate through our Airfield Operations office. Civilian small UAS operators within PMD Class Delta airspace are required to hold an FAA Part 107 certificate. Operating over the airport and any adjoining plant property requires an additional Special Government Interest (SGI) airspace waiver 9-ATOR-HQ-SOSC@faa.gov . Our office may assist with this coordination.

7. Section 4: Additional Information

1. Please provide any additional information or guidance that would be helpful for contractors planning to conduct sUAS operations on your installation. Vetting through Security Forces of all personnel is required prior to entering Plant 42, airfield or adjacent contractor sites.

References:

• Air Force Manual (AFMAN) 11-502, Small Unmanned Aircraft Systems (sUAS): Provides comprehensive guidance on the operation of sUAS within the Air Force, including airworthiness, airspace authorization, training, and safety procedures.

• Federal Aviation Administration (FAA) Title 14 of the Code of Federal Regulations (14 CFR Part 107): Outlines the FAA's regulations for the commercial operations of small, unmanned aircraft systems, covering areas like airspace restrictions, pilot certification, and operational limitations.

• DIU "Blue" sUAS Platform List: Identifies commercially available sUAS platforms that have undergone a formal evaluation and approval process by the Defense Innovation Unit.

• DoDD 5200.01, DoD Information Security Program: Establishes the Department of Defense's overarching framework for protecting classified and controlled unclassified information.

• DoDI 8500.01, Cybersecurity for the Department of Defense: Outlines cybersecurity requirements for all DoD information systems, including those used to process and store sUAS imagery.

mailto:9-ATOR-HQ-SOSC@faa.gov

Altus AFB / Clinton Sherman installation in preparation for the upcoming FY25 pavement inspection contract. This information will be used to inform potential contractors/bidders and ensure safe and compliant sUAS operations.

Background: In recent pavement inspection contract solicitations, the Air Force Civil Engineer Center (AFCEC) has received competitive proposals incorporating the use of contractor-owned and operated sUAS platforms to collect downward-facing (nadir) imagery of some or all pavement surfaces (airfields, roads, and parking areas) for distress inventory and Pavement Condition Index (PCI) assessment. Several benefits of this proposed data collection methodology above traditional manual inspection methods include 100% geolocated distress inventory and image capture, which may result in:

• Improved scope definition for airfield preventative and corrective maintenance and repair projects

• Provide for a photographic record of “ground truth” for a given inspection

• Eliminates redundant work for installations in the form of separate project-level surface condition inspections

• Enhanced survey repeatability

In order to ensure that these proposals are fairly considered in upcoming contract solicitations, it is necessary for AFCEC to understand and define installation-specific operational requirements and restrictions so that contractors can tailor their proposals accordingly.

Assumptions:

• The contractor will be using a COTS sUAS platform/sensor payload from the DIU’s "Blue" list located at: https://www.diu.mil/blue-uas-cleared-list.

• The contractor will have completed all necessary external approvals (e.g., COTS exemption, ETP, FAA certifications) prior to requesting installation-specific approvals.

• The contractor will be responsible for implementing and maintaining robust data security measures throughout all phases of the project, including data collection, processing, storage, and transmission. These measures will comply with all applicable DoD and Air Force cybersecurity regulations and policies.

Questionnaire:

Section 1: sUAS Program Point of Contact

1. Does your installation have a designated Installation Project Management Office (IPMO) or sUAS Program Manager responsible for overseeing sUAS operations?

o Yes ☐ No ☐ - this is in development, it will most likely be me.

o Name: Troy Bame o Title: Airspace Manager o Email Address: troy.bame@us.af.mil o Phone Number: DSN 866-7804, commercial 580-481-7804

Section 2: Airspace and Operational Approvals

1. What are the specific steps a contractor must take to obtain approval to operate a sUAS within your installation's airspace? Please provide a detailed explanation or a link to relevant instructions/procedures. – procedures are in development

2. Does your installation have an approved CONEMP or guidance document that contractors must utilize?

o Yes ☐ No ☐

3. If yes, please provide a copy of the CONEMP or guidance document.

4. Is there a certain frequency spectrum the contractor would have to operate under (e.g., 2.4 GHz, 5 GHz, etc.)? Would the contractor be assigned a temporary frequency? Unknown at this time.

Section 3: Image Collection Restrictions and Limitations

1. Are there any specific areas on the installation where sUAS flights are strictly prohibited (e.g., near sensitive facilities, critical infrastructure, or ongoing construction projects)?

Please provide a detailed list and/or map. Yes, it will be contained in the CONEMP upon publication

2. Are there any restrictions on capturing imagery of specific assets or areas? Examples include:

o Aircraft tail numbers: Yes ☐ No ☐ o Building facades: Yes ☐ No ☐ o Security checkpoints: Yes ☐ No ☐ o Other (please specify):

3. Are there any altitude restrictions for sUAS operations on the installation?

o Yes ☐ No ☐

4. If yes, please specify the maximum permitted altitude(s):

o 200’ AGL is the expected ceiling

5. Are there any specific time-of-day restrictions for sUAS operations (e.g., prohibited during specific hours, limited to daylight operations only)?

o Yes ☐ No ☐

6. If yes, please specify the permitted operating hours:

o Field operating hours are 0900-0230L Mon-Fri. Recommend smaller portions be completed during the period after sunrise and before 0900 or on the weekends.

7. Are there any other unique restrictions, limitations, or considerations related to sUAS operations on your installation that contractors should be aware of?

o Yes, see above.

Section 4: Additional Information

1. Please provide any additional information or guidance that would be helpful for contractors planning to conduct sUAS operations on your installation.

1. Our CONEMP development is in the infancy stages, unknown when it will be complete. We have received a waiver from our HHQ for one off situations before. If the contractor would like to complete operations before CONEMP completion, we will staff an ETP waiver.

References:

• Air Force Manual (AFMAN) 11-502, Small Unmanned Aircraft Systems (sUAS): Provides comprehensive guidance on the operation of sUAS within the Air Force, including airworthiness, airspace authorization, training, and safety procedures.

• Federal Aviation Administration (FAA) Title 14 of the Code of Federal Regulations (14 CFR Part 107): Outlines the FAA's regulations for the commercial operations of small unmanned aircraft systems, covering areas like airspace restrictions, pilot certification, and operational limitations.

• DIU "Blue" sUAS Platform List: Identifies commercially available sUAS platforms that have undergone a formal evaluation and approval process by the Defense Innovation Unit.

• DoDD 5200.01, DoD Information Security Program: Establishes the Department of Defense's overarching framework for protecting classified and controlled unclassified information.

• DoDI 8500.01, Cybersecurity for the Department of Defense: Outlines cybersecurity requirements for all DoD information systems, including those used to process and store

Arnold AFB

Included Documents: No Response

Columbus AFB / Shuqualak AAF

Included Documents: No Response, No Drone Zone

Dobbins ARB installation in preparation for the upcoming FY25 pavement inspection contract. This information will be used to inform potential contractors/bidders and ensure safe and compliant sUAS operations.

Background: In recent pavement inspection contract solicitations, the Air Force Civil Engineer Center (AFCEC) has received competitive proposals incorporating the use of contractor-owned and operated sUAS platforms to collect downward-facing (nadir) imagery of some or all pavement surfaces (airfields, roads, and parking areas) for distress inventory and Pavement Condition Index (PCI) assessment. Several benefits of this proposed data collection methodology above traditional manual inspection methods include 100% geolocated distress inventory and image capture, which may result in:

• Improved scope definition for airfield preventative and corrective maintenance and repair projects

• Provide for a photographic record of “ground truth” for a given inspection

• Eliminates redundant work for installations in the form of separate project-level surface condition inspections

• Enhanced survey repeatability

In order to ensure that these proposals are fairly considered in upcoming contract solicitations, it is necessary for AFCEC to understand and define installation-specific operational requirements and restrictions so that contractors can tailor their proposals accordingly.

Assumptions:

• The contractor will be using a COTS sUAS platform/sensor payload from the DIU’s "Blue" list located at: https://www.diu.mil/blue-uas-cleared-list.

• The contractor will have completed all necessary external approvals (e.g., COTS exemption, ETP, FAA certifications) prior to requesting installation-specific approvals.

• The contractor will be responsible for implementing and maintaining robust data security measures throughout all phases of the project, including data collection, processing, storage, and transmission. These measures will comply with all applicable DoD and Air Force cybersecurity regulations and policies.

Questionnaire:

Section 1: sUAS Program Point of Contact

1. Does your installation have a designated Installation Project Management Office (IPMO) or sUAS Program Manager responsible for overseeing sUAS operations?

o Yes ☑ No ☐ o Name: MSgt Christopher Hyde o Title: NCOIC, Plans and Programs o Email Address: christopher.hyde@us.af.mil o Phone Number: 678-655-4907 within your installation's airspace? Please provide a detailed explanation or a link to relevant instructions/procedures.

Must be routed through Dobbins Air Traffic Control Manager for approval. She can be reached at 678-655-5149. Mrs Dina Tomczak or dina.tomczak.1@us.af.mil

a. UAS PIC must employ the use of Geo-fencing technology to ensure the UAS remains within the confines of the designated operating area.

b. UAS PIC must email MGE ATCT at 94OG.OGT.UAS@us.af.mil the day prior to flying operations and provide location of flight, as identified on UASFM, with name and contact information of PIC and time of operations.

c. On each date of UAS operation, the UAS PIC must establish telephone contact with the MGE ATCT at least fifteen (15) minutes prior to operating at 678-655-7058 to provide (real time) start and stop times. Do not operate UAS if contact with MGE ATCT is unsuccessful (no answer).

d. MGE ATCT may disapprove, terminate, restrict, or delay UAS flight operations covered by this authorization at any time.

2. Does your installation have an approved CONEMP or guidance document that contractors must utilize?

o Yes ☐ No ☑

The Dobbins contracting office does conduct post award conferences with contractors and all key installation stakeholders to provide necessary information for contractors to operate on the installation.

3. If yes, please provide a copy of the CONEMP or guidance document.

4. Is there a certain frequency spectrum the contractor would have to operate under (e.g., 2.4 GHz, 5 GHz, etc.)? Would the contractor be assigned a temporary frequency?

If a contractor wanted to fly a sUAS on base at this time they would not need a temporary frequency if it were COTS. If it is not COTS they would need a J/F-12, IRAC, and SCS published, and they submit a request for temporary frequencies which would take minimum of 90 days to be approved.

mailto:dina.tomczak.1@us.af.mil

Section 3: Image Collection Restrictions and Limitations

1. Are there any specific areas on the installation where sUAS flights are strictly prohibited (e.g., near sensitive facilities, critical infrastructure, or ongoing construction projects)?

Please provide a detailed list and/or map.

2. The entire installation is restricted without specific written approval through FAA, Dobbins Base Operations, Public Affairs, and Security Forces and the Lockheed Martin properties;

South and North Campuses.

3. Are there any restrictions on capturing imagery of specific assets or areas? Examples include:

Imagery, photography, videography must be authorized by the 94 AW Commander via Public Affairs and Security Forces – this pertains to all areas on the installation in accordance with USC § 795, Photographing and Sketching Defense Installations, and Executive Order 10104, Defining Certain Vital Military and Navy Installations and Equipment as Requiring Protection Against the General Dissemination of Information Relative Thereto.

o Aircraft tail numbers: Yes ☑ No ☐ o Building facades: Yes ☑ No ☐ o Security checkpoints: Yes ☑ No ☐ o Other (please specify):

4. Are there any altitude restrictions for sUAS operations on the installation?

o Yes X No ☐

If yes, please specify the maximum permitted altitude(s): 400 ft AGL

5. Are there any specific time-of-day restrictions for sUAS operations (e.g., prohibited during specific hours, limited to daylight operations only)?

o Yes X No ☐

6. If yes, please specify the permitted operating hours:

NOTE: ATC does not separate manned vs unmanned.

Hours of operations: Mon – Fri 0800L – 2300L, Sat – Sun 0800L – 1600L, Closed Federal Holidays and at other time IAW NOTAM’d closures

7. Are there any other unique restrictions, limitations, or considerations related to sUAS operations on your installation that contractors should be aware of?

Section 4: Additional Information

1. Please provide any additional information or guidance that would be helpful for contractors planning to conduct sUAS operations on your installation.

comprehensive guidance on the operation of sUAS within the Air Force, including airworthiness, airspace authorization, training, and safety procedures.

• Federal Aviation Administration (FAA) Title 14 of the Code of Federal Regulations (14 CFR Part 107): Outlines the FAA's regulations for the commercial operations of small unmanned aircraft systems, covering areas like airspace restrictions, pilot certification, and operational limitations.

• DIU "Blue" sUAS Platform List: Identifies commercially available sUAS platforms that have undergone a formal evaluation and approval process by the Defense Innovation Unit.

• DoDD 5200.01, DoD Information Security Program: Establishes the Department of Defense's overarching framework for protecting classified and controlled unclassified information.

• DoDI 8500.01, Cybersecurity for the Department of Defense: Outlines cybersecurity

Grissom ARB

- Approved CONEMP installation in preparation for the upcoming FY25 pavement inspection contract. This information will be used to inform potential contractors/bidders and ensure safe and compliant sUAS operations.

Background: In recent pavement inspection contract solicitations, the Air Force Civil Engineer Center (AFCEC) has received competitive proposals incorporating the use of contractor-owned and operated sUAS platforms to collect downward-facing (nadir) imagery of some or all pavement surfaces (airfields, roads, and parking areas) for distress inventory and Pavement Condition Index (PCI) assessment. Several benefits of this proposed data collection methodology above traditional manual inspection methods include 100% geolocated distress inventory and image capture, which may result in:

• Improved scope definition for airfield preventative and corrective maintenance and repair projects

• Provide for a photographic record of “ground truth” for a given inspection

• Eliminates redundant work for installations in the form of separate project-level surface condition inspections

• Enhanced survey repeatability

In order to ensure that these proposals are fairly considered in upcoming contract solicitations, it is necessary for AFCEC to understand and define installation-specific operational requirements and restrictions so that contractors can tailor their proposals accordingly.

Assumptions:

• The contractor will be using a COTS sUAS platform/sensor payload from the DIU’s "Blue" list located at: https://www.diu.mil/blue-uas-cleared-list.

• The contractor will have completed all necessary external approvals (e.g., COTS exemption, ETP, FAA certifications) prior to requesting installation-specific approvals.

• The contractor will be responsible for implementing and maintaining robust data security measures throughout all phases of the project, including data collection, processing, storage, and transmission. These measures will comply with all applicable DoD and Air Force cybersecurity regulations and policies.

Questionnaire:

Section 1: sUAS Program Point of Contact

1. Does your installation have a designated Installation Project Management Office (IPMO) or sUAS Program Manager responsible for overseeing sUAS operations?

o Yes ☑ No ☐ o Name: Keith Atkinson o Title: Air Traffic Control Systems Equipment Program Manager o Email Address: keith.atkinson.4@us.af.mil o Phone Number: 765-688-4399 within your installation's airspace? Please provide a detailed explanation or a link to relevant instructions/procedures.

We will need to be contacted well in advance of the operations being scheduled to ensure that there are no conflicts. Our flying schedule is very fluid and we have several exercises throughout the year. All of the coordination between security forces, public affairs, airfield management, and air traffic will be done locally by the contact listed above.

2. Does your installation have an approved CONEMP or guidance document that contractors must utilize?

o Yes ☑ No ☐

We do have an approved CONEMP but it is a standardized one that is used by most AFRC bases so all operational approvals and restrictions will be done locally. However, because the contractor is not affiliated with the base directly, we may require them to receive a FAA Certificate of Authorization (COA) for the activity. This can be discussed upon contract approval.

3. If yes, please provide a copy of the CONEMP or guidance document.

Attached to email

4. Is there a certain frequency spectrum the contractor would have to operate under (e.g., 2.4 GHz, 5 GHz, etc.)? Would the contractor be assigned a temporary frequency?

No

Section 3: Image Collection Restrictions and Limitations

1. Are there any specific areas on the installation where sUAS flights are strictly prohibited (e.g., near sensitive facilities, critical infrastructure, or ongoing construction projects)?

Please provide a detailed list and/or map.

We have a prison that borders the property on the Southeast corner that is prohibited to fly over. Our base is also unique in that some of the property is not contiguous, so depending on what the mission is, the contracted party may need an additional FAA Certificate of Authorization if they plan on traversing over civilian owned areas to get from one part of the base property to another. This should be able to be included in a singular FAA COA for the entire operation. There may be other sensitive areas that will need to be discussed based on mission requirements. There are also other sensitive security information we may need including Radio ID number, PIC Credentials and information, and sUAS registration information.

2. Are there any restrictions on capturing imagery of specific assets or areas? Examples include:

o Aircraft tail numbers: Yes ☑ No ☐ o Building facades: Yes ☑ No ☐ Possibly o Security checkpoints: Yes ☑ No ☐ o Other (please specify): Please refer to question 1 in this section.

3. Are there any altitude restrictions for sUAS operations on the installation?

o Yes ☑ No ☐

4. If yes, please specify the maximum permitted altitude(s): 400’. This altitude is standard but if mission requirements dictate a higher altitude, there may be additional approvals that need to be acquired. Our CONEMP does state that 1000’ AGL may be flown but anything over 400’ would need to be included in a COA.

5. Are there any specific time-of-day restrictions for sUAS operations (e.g., prohibited during specific hours, limited to daylight operations only)?

o Yes ☑ No ☐

6. If yes, please specify the permitted operating hours: During flight operations.

7. Are there any other unique restrictions, limitations, or considerations related to sUAS operations on your installation that contractors should be aware of? See question 1. Our flight operations are not at regular intervals, so prior coordination is citical.

Section 4: Additional Information

1. Please provide any additional information or guidance that would be helpful for contractors planning to conduct sUAS operations on your installation.

All information is discussed above.

comprehensive guidance on the operation of sUAS within the Air Force, including airworthiness, airspace authorization, training, and safety procedures.

• Federal Aviation Administration (FAA) Title 14 of the Code of Federal Regulations (14 CFR Part 107): Outlines the FAA's regulations for the commercial operations of small unmanned aircraft systems, covering areas like airspace restrictions, pilot certification, and operational limitations.

• DIU "Blue" sUAS Platform List: Identifies commercially available sUAS platforms that have undergone a formal evaluation and approval process by the Defense Innovation Unit.

• DoDD 5200.01, DoD Information Security Program: Establishes the Department of Defense's overarching framework for protecting classified and controlled unclassified information.

• DoDI 8500.01, Cybersecurity for the Department of Defense: Outlines cybersecurity

DEPARTMENT OF THE AIR FORCE

AIR FORCE RESERVE COMMAND

MEMORANDUM FOR 434 ARW/CC

FROM: HQ AFRC/A4P

549 Robins Parkway Robins AFB GA 31098-2005

SUBJECT: Concept of Employment (CONEMP) for Small Unmanned Aircraft System (sUAS) Operations at Grissom ARB.

1. Mission and Objectives. The AFRC GI&S sUAS Program Office will provide for the safe and effective integration of sUAS capability across the Command. Updates to installation aerial imagery utilizing unmanned aircraft would greatly reduce costs compared to manned aircraft solutions currently employed.

2. CONEMP Overview. This CONEMP describes how the AFRC GI&S sUAS Program Office will conduct sUAS operations and will comply with all applicable federal laws and DoD policies.

3. Responsibilities. The AFRC GI&S sUAS Program Office has been delegated overall responsibility and must ensure that all required guidance in AFMAN 11-502 is followed by all sUAS operators.

4. Training and Certification.

4.1. The AFRC GI&S sUAS Program Office supervisor will approve entry into the sUAS operator Initial Training (IT) and instructor upgrade programs.

4.2. The sUAS operator IT and instructor upgrade programs are executed IAW the AFSOC/A3OU-approved training plans and will be documented on AF Form 1381.

4.3. Upgrade training will be conducted by certified sUAS instructors.

4.4. sUAS operator and instructor certifications are annotated on AF Form 1381 and maintained by the AFRC GI&S sUAS Program Office.

4.5. sUAS certification is valid for 24 months, with another certification by a sUAS instructor required after this period.

5. Currency.

5.1. To be considered current, a SUAS operator must perform one live sortie every 90 days. Currency will be tracked via the Small Unmanned Aircraft Systems Manager (SUASMAN) web application, a single source web-enabled database for tracking sUAS-O certifications, flight logs, currency, training accomplishments and sUAS logistics management. The 90-day requirement will be rolling and based off the IT date, re-currency/re-qualification date, or completion of the last live flight within the required 90 days.

5.2. The duration of loss of currency time is from the date the sUAS operator became non- current until the specific retraining start date. Non-current sUAS operators are not authorized to operate sUAS unless under the supervision of a sUAS instructor. sUAS operator re-currency requirements are as follows:

5.2.1. Loss of currency Up To 6 Months. A sUAS operator will conduct a live fight with a sUAS instructor.

5.2.2. Loss of currency Up to 24 Months. A sUAS operator who is non-current exceeding 6 months, or who did not accomplish the required 24-month certification prior to the last day of the 24th month, will accomplish the ground and flight certification with a sUAS instructor.

5.2.3. Loss of currency exceeding 24 months requires re-accomplishment of IT.

6. Cyber Security. No operations to include purchasing, turning on any sUAS equipment, or removing sUAS from boxes will take place until an AF cyber security exemption has been approved IAW AFMAN 11-502, paragraph 2.4. Cover the camera lenses when the sUAS is not in use. The sUAS Management Office will maintain the cyber security exemption on file and ensure that each operator is trained on the mitigations. Document training on AF Form 1381 and filed in SUASMAN.

7. Domestic Privacy Concerns. Operations prescribed within this CONEMP fall within the “DoD Installation Support within Airspace Delegated by the FAA for DoD Use” and “Other Authorized Missions within airspace delegated by the FAA for DoD Use”, which will require installation commander approval. Refer to AFMAN 11-502 Attachment 8. Installation commander (434 ARW/CC) signature on this CONEMP constitutes approval.

8. Spectrum deconfliction and approval will be accomplished with the base spectrum manager before any sUAS operations commence for the applicable sUAS platform. The AFRC/A6OS Spectrum Management office will determine if the sUAS platform meets the criteria and able to be certified under the FCC as a Part 15 device IAW Title 47 of the Code of Federal Regulations, Part 15C. The sUAS will utilize frequencies in the “unlicensed” band and may cause interference. Prior to launching, the sUAS operator will turn the equipment on and if any abnormalities are noticed, will not launch.

9. Coordination with applicable agencies. The sUAS Management Office will provide a flight schedule to local OSS/OSAT (Control Tower) and local SFS (Security Force Desk) at least 3 business days prior to any scheduled sUAS flight. Any changes will be coordinated. In the event an unscheduled flight is required to support emergency response personnel, coordination with the aforementioned offices will occur prior to flight.

10. Operational Area Description. sUAS will ONLY be flown within the designated boundaries of the flight plan at or below 1000’ above ground level.

11. Flight Approval Procedures. The AFRC GI&S sUAS Program Office has been delegated flight approval authority.

11.1. The AFRC GI&S sUAS Program Office will ensure that a Federal Aviation Administration (FAA) COA has been approved prior to any operations and ensure that each operator is knowledgeable on the COA requirements.

12. Risk Management. The lead sUAS operator will complete a risk management assessment IAW AFMAN 11-502 prior to all sUAS operations.

13. Communication requirements. Prior to launching the sUAS, the lead sUAS operator will contact the local Control Tower and obtain approval. Operator will notify Control Tower when operations are complete.

14. Deconfliction. sUAS operations will ONLY occur within the designated and deconflicted sUAS areas at or below 1000’ above ground level and IAW the FAA COA.

14.1. Visual observers will accompany sUAS operators and will maintain visual contact with the sUAS and surrounding airspace at all times during flight operations.

15. Night operations are authorized if the operators and visual observers are in place 30 minutes prior to launching to acclimatize their vision. Aircraft lighting, if installed, must be on.

16. Contingencies. Immediately land the sUAS if it becomes unresponsive to control inputs or performs abnormally. Immediately contact local Control Tower if the sUAS departs the approved area. Provide last known altitude and direction of flight. Notify the AFRC GI&S sUAS Program Office, DSN 497-2105, who will notify local Base Safety. If required, the sUAS Program Management Office will complete a Mishap Report IAW AFMAN 11-502.

17. Personal Protective Equipment. All sUAS operators will wear appropriate safety PPE when launching the sUAS.

18. This CONEMP is in compliance with applicable federal law and policy, and applicable state and local law.

KIT W. ALLEN, Lt Col, USAF Chief, Resources & Integration Division

1st Ind, 434 ARW/CC

MEMORANDUM FOR HQ AFRC/A4P

Concept of Employment (CONEMP) for sUAS Operations on Grissom ARB is approved.

Thomas O. Pemberton, Col, USAF Commander, 434 Air Refueling Wing

Joint Base McGuire-Dix-Lakehurst (JBMDL)

- Approved CONEMP

- UAS Sector Map installation in preparation for the upcoming FY25 pavement inspection contract. This information will be used to inform potential contractors/bidders and ensure safe and compliant sUAS operations.

Background: In recent pavement inspection contract solicitations, the Air Force Civil Engineer Center (AFCEC) has received competitive proposals incorporating the use of contractor-owned and operated sUAS platforms to collect downward-facing (nadir) imagery of some or all pavement surfaces (airfields, roads, and parking areas) for distress inventory and Pavement Condition Index (PCI) assessment. Several benefits of this proposed data collection methodology above traditional manual inspection methods include 100% geolocated distress inventory and image capture, which may result in:

• Improved scope definition for airfield preventative and corrective maintenance and repair projects

• Provide for a photographic record of “ground truth” for a given inspection

• Eliminates redundant work for installations in the form of separate project-level surface condition inspections

• Enhanced survey repeatability

In order to ensure that these proposals are fairly considered in upcoming contract solicitations, it is necessary for AFCEC to understand and define installation-specific operational requirements and restrictions so that contractors can tailor their proposals accordingly.

Assumptions:

• The contractor will be using a COTS sUAS platform/sensor payload from the DIU’s "Blue" list located at: https://www.diu.mil/blue-uas-cleared-list.

• The contractor will have completed all necessary external approvals (e.g., COTS exemption, ETP, FAA certifications) prior to requesting installation-specific approvals.

• The contractor will be responsible for implementing and maintaining robust data security measures throughout all phases of the project, including data collection, processing, storage, and transmission. These measures will comply with all applicable DoD and Air Force cybersecurity regulations and policies.

Questionnaire:

Section 1: sUAS Program Point of Contact

1. Does your installation have a designated Installation Project Management Office (IPMO) or sUAS Program Manager responsible for overseeing sUAS operations?

o Yes ☒ No ☐ o Name: Michael Polhemus o Title: Director, JBMDL UAS Detachment o Email Address: michael.polhemus.1@us.af.mil o Phone Number: 609-754-3745 within your installation's airspace? Please provide a detailed explanation or a link to relevant instructions/procedures.

• Contractor will be required to demonstrate compliance with DoD requirements for operating a UAS on a DoD installation in accordance with previously cited assumptions

• Contractor will need to provide a detailed plan to the installation (via the POC) for UAS operations. Upon receipt and review, installation will issue authorization to operate within the SSI area.

• Contractor will be responsible for obtaining FAA CoA

• Spectrum authorization through the local spectrum manager will also be required before flight operations can begin

• Local ATC will want an opportunity to discuss plan with contractor to deconflict with installation flight operations

2. Does your installation have an approved CONEMP or guidance document that contractors must utilize?

o Yes ☒ No ☐

3. If yes, please provide a copy of the CONEMP or guidance document.

4. Is there a certain frequency spectrum the contractor would have to operate under (e.g., 2.4 GHz, 5 GHz, etc.)? Would the contractor be assigned a temporary frequency? Installation spectrum manager would review UAS operations frequencies but to date, there have been no constraints placed on contractor systems.

5.

Section 3: Image Collection Restrictions and Limitations

1. Are there any specific areas on the installation where sUAS flights are strictly prohibited (e.g., near sensitive facilities, critical infrastructure, or ongoing construction projects)?

Please provide a detailed list and/or map. UAS operations would not be permitted within the existing R5001 Restricted Area. Additionally, Navy flight test operations within their zone of the installation may involve sensitive aircraft or equipment. Coordination with them will be required prior to UAS operations in the vicinity. Additionally, there are two prison complexes on the installation that are considered no-fly/no imagery area. A federal prison is in the immediate vicinity of the primary runway at McGuire. A NJ State prison is farther away from the runway but still should be considered in planning flight operations.

2. Are there any restrictions on capturing imagery of specific assets or areas? Examples include:

o Aircraft tail numbers: Yes ☐ No ☒ o Building facades: Yes ☐ No ☒ o Security checkpoints: Yes ☒ No ☐ o Other (please specify): The installation periodically supports mission sets for which there may be OPSEC concerns associated will captured imagery. These events are infrequent. Also see previous comments regarding the prison facilities.

3. Are there any altitude restrictions for sUAS operations on the installation?

o Yes ☐ No ☒ Normal FAA rules apply.

4. If yes, please specify the maximum permitted altitude(s):

5. Are there any specific time-of-day restrictions for sUAS operations (e.g., prohibited during specific hours, limited to daylight operations only)?

o Yes ☒ No ☐

6. If yes, please specify the permitted operating hours: UAS operations would need to be conducted outside the normal daily launch and recovery windows for installation aircraft.

7. Are there any other unique restrictions, limitations, or considerations related to sUAS operations on your installation that contractors should be aware of? None

Section 4: Additional Information

1. Please provide any additional information or guidance that would be helpful for contractors planning to conduct sUAS operations on your installation. It may be important to understand that the McGuire airfield is under the control of Air Force controllers. The Lakehurst airfield is under the control Navy Controllers (who provide the ATC service on behalf of the Air Force). Both ATC facilities would need to be involved in planning conversations.

comprehensive guidance on the operation of sUAS within the Air Force, including airworthiness, airspace authorization, training, and safety procedures.

• Federal Aviation Administration (FAA) Title 14 of the Code of Federal Regulations (14 CFR Part 107): Outlines the FAA's regulations for the commercial operations of small unmanned aircraft systems, covering areas like airspace restrictions, pilot certification, and operational limitations.

• DIU "Blue" sUAS Platform List: Identifies commercially available sUAS platforms that have undergone a formal evaluation and approval process by the Defense Innovation Unit.

• DoDD 5200.01, DoD Information Security Program: Establishes the Department of Defense's overarching framework for protecting classified and controlled unclassified information.

• DoDI 8500.01, Cybersecurity for the Department of Defense: Outlines cybersecurity

A/O 6 Mar 2024

CONCEPT OF EMPLOYMENT

SMALL UNMANNED AIRCRAFT SYSTEMS (sUAS)

Operations Program Directive

JOINT BASE MCGUIRE-DIX-LAKEHURST

TABLE OF CONTENTS

1. Overview

2. Compliance

3. Mission and Objectives

4. Responsibilities

5. Training and Certifications

6. Currency

7. Personal Protective Equipment

8. Cyber Security

9. Domestic Privacy Concerns

10. Electromagnetic, Radio Frequency, and Spectrum Approval

11. Coordination with Applicable Agencies

12. Operational Area Description and Conditions

13. Flight Approval and Procedures

14. Night Operations

15. Dropping of Objects

16. Risk Management

17. Emergency Procedures and Contingencies

18. Communication Requirements

19. Deconfliction

20. Mishap Reporting

21. Review/Signatories

Attachment 1 Glossary of References and Supporting Information

Attachment 2 sUAS Operation Area Depiction

Attachment 3 Flight Operations Quick Reference Checklist

Attachment 4 Template for Unit/Agency Annex

Attachment 5 Beyond Visual Line of Sight

Attachment 6 JB MDL UAS Detachment

Attachment 7 R5001 Considerations

Annexes Approved Units/Agencies

1. OVERVIEW:

1.1. This Concept of Employment (CONEMP)/Small Unmanned Aircraft System (sUAS) Operations Program Directive outlines responsibilities, rules, and procedures for sUAS operations (Groups 1-3) within Joint Base McGuire-Dix-Lakehurst (JB MDL) Special Security Instruction (SSI) airspace and certifies compliance with Department of Defense (DoD) policy and federal law.

2. AUTHORITIES AND COMPLIANCE:

2.1. JB MDL provides a complex environment to operate sUAS. The full array of authorities to operate sUAS on the installation are distributed among separate command entities. The installation commander, 87 ABW/CC, holds authorities for permitting the launch, flight, and recovery of sUAS within the lateral confines of the installation boundaries, also referred to as the FAA Special Security Instruction (SSI) area. Separate from these authorities, the FAA has delegated the airspace at JB MDL to the Senior Airfield Authority, fulfilled by the 305 AMW/CC. There is also an FAA-designated Restricted Area (R5001) at JB MDL which, while active, is under the authority of the US Army Support Activity Ft Dix Commander. Based on the distributed authorities, all three entities (87 ABW/CC, 305 AMW/CC and ASA Commander) must approve sUAS operations at JB MDL.

2.2 This directive applies to all JB MDL assigned units (encompassing all services/components) and tenant partners.

2.3. Unit/agency Annex incorporation into this directive signifies authorization, acceptance, and understanding of all policy requirements. In cases where USAF policy is referenced, service component equivalents may be substituted provided they meet an equal or higher standard, as determined by the JB MDL sUAS Program Manager. Refer to Attachment 4 for Unit Annex requirements.

2.4. Non-base assigned personnel/units/agencies (i.e. transient, deployed) must formalize their request for UAS operations in accordance with AFMAN 11-502 (AMC Supplement), Small Unmanned Aircraft Systems and receive JB MDL Installation Commander and SAA written endorsement. If these operations are to occur strictly within R5001 airspace, refer to Attachment 7.

2.5. To promote the effective employment of the sUAS program, JB MDL has established JB MDL UAS Detachment. Refer to Attachment 6 of this publication for establishment details. UAS Det is responsible for the oversight and management of this CONEMP/directive.

3. MISSION AND OBJECTIVES:

3.1. This directive is intended to promote the safe integration of sUAS operations in a complex flying environment and standardize procedures between approved military and/or civilian entities and Air Traffic Control servicing facilities. JB MDL mission sets vary broadly, therefore this directive allows flexibility for a host of sUAS purposes including maintenance, logistics, engineering, security, contingencies, training, and many others.

3.2. Units/agencies are responsible for detailing specific mission and objectives via Annex. Refer to AFMAN 11-502 (AMC Supplement), Small Unmanned Aircraft Systems, Attachment 8 for specific domestic use purposes. Annex submission requirements are outlined in paragraph 4.2.2. and Attachment 4 (Template for Unit/Agency Annex) of this directive.

3.3. The scope of this directive is limited to JB MDL and those responsible for airspace and air operations, IAW AFMAN 11-502 (AMC Supplement), Small Unmanned Aircraft Systems.

3.4. sUAS will not be used to collect information solely for the purpose of monitoring activities protected by the First Amendment or the lawful exercise of other rights secured by the Constitution or laws of the United States. Refer to Paragraph 9 for additional information.

4. RESPONSIBILITIES:

4.1. JB MDL Installation UAS Program Manager will:

4.1.1. Provide program oversight and ensure organizational compliance with all applicable administrative requirements.

4 agent with responsibility, and Senior Airfield , to review for compliance and approve requests from units/agencies for sUAS operations under this CONEMP, unless…