www.arsconsulting.net ALTERNATIVES RENEWAB LE SOLUTIONS, LLC 1725 I Street, NW, Suite 300, Washington, DC 20006 

# ARS FLIGHT SAFETY & PROCEDURES MANUALARS Flight Safety and Procedures Manual Rev. 3.13.15 1 

### TABLE OF CONTENTS TABLE OF CONTENTS ................................ ................................ ................................ ................................ ..... 1 1.0 Flight Plan & Assessment ................................ ................................ ................................ .................. 0 2.0 PRE- FLIGHT CHECK LIST ................................ ................................ ................................ ..................... 1 3.0 Flight Procedures ................................ ................................ ................................ .............................. 3 4.0 Pre/Post Landing Procedures ................................ ................................ ................................ ............ 4 5.0 Equivalent Level of Safety Requirements ................................ ................................ ......................... 5 6.0 Spec ific Operational Procedures for Pilots ................................ ................................ ....................... 7 6.1 Specific Operational Procedures for Aerial Building Photography & Inspections ............................. 7 6.2 Specific Operational Procedures for Construction Sites ................................ ................................ ..... 7 6.3 Specific Operational Procedures for Temporary Tower Crane Assembly Verification Inspections .... 8 6.4 Specific Operational Procedures for Substructure Bridge Inspections ................................ ............. 10 6.5 Specific Operational Procedures for the DC Special Flight Rules Area (DC SFRA), including the DC Metropolitan Area Flight Restricted Zone (DC FRZ) ................................ ................................ ................ 11

### 1.0 Flight Plan & Assessment A. Flight Plan for Subject Location :

_________________________________________________________________

_________________________________________________________________

_________________________________________________________________

_________________________________________________________________ B. Check weather conditions for rain, fog and wind speed. 1. Weather: _____________________________ 2. Visibility: _________________

___________ 3. Wind Speed (NOAA):____________________ 4. Proximity to Airport:____________________ i. Was Airport notified: Yes or No Date:______ Time:_______ ii. POC:______________________(if yes) C. What is the nearest intersection:___________________________ 1. Distance to intersection or road:___________________ 2. Distance & location to driveways or parking structures:________________ D. Distance to nearest home or building structure:_______________________ 1. Is property land locked on sides (Left, Right or Both):_____

____________ 2. Is property land locked in rear (with access or not):__________________ E. Obstacles: 1. Are phone/cable lines in flight plan zone? Yes:_____ No:______ If yes, note areas(s)_____________________________________________ 2. Are trees in flight plan zon e? Yes:_____ No:______ If yes, note areas(s)_____________________________________________ 3. Are structures or obstacles in flight plan zone? Yes:_____ No:______ If yes, note areas(s)_____________________________________________ F. Flight Plan Adjustments: If required, provide new flight plan to adjust to obstacles: ____________________________________________________

_____________________________________________________________

_____________________________________________________________ G. Mark off flight pla n zone with yellow tape and signs . 1. Close off ground level area for the flight path of UAS. 2. Place orange cones outlining ground flight area. H. Begin Pre- Flight Checklist .ARS Flight Safety and Procedures Manual Rev. 3.13.15 1 2.0 

### PRE

- FLIGHT CHECK LIST A. Visually inspect shell and other plastic components for cracking/damage (landing skids, camera mounting plates, etc.) 1. Check tightness of motor retaining screws and shell retaining screws with 2mm hex. 2. Check data springe pins and battery contact pads for erosion. Clean as needed. B. Check remote controller, smart battery, and range extender are properly functioning and are fully charged. C. Ensure gimbal clamp and lens cap has been removed. D. Check camera for any damage. E. Check anti -drop kits have been mounted correctly. F. Place micro-SD card into camera and ensure its locked . G. Put on neckstrap and hook up remote controller H. Set S1 and S2 Switches to up position. I. Move antenna to vertical position. J. Install 4 props on UAS using proper protocols. K. Install main battery and check battery levels in UAS. L. Check gimbal is functioning as normal and camera angel. M. Start FPV App and check functionality. N. Begin Flight Procedures.ARS Flight Safety and Procedures Manual Rev. 3.13.15 2ARS Flight Safety and Procedures Manual Rev. 3.13.15 3 

### 3.0 Flight Procedures A. Was the Pre- Flight Checklist conducted? Yes or No. B. Place UAS on open flat ground or surface with battery indicators facing pilot. a. UAS should be placed in clear and safe launch and recovery position if it returns to home. C. Power on remote controller and range extender, then the UAS smart battery. a. Power ON remote controller. b. Power ON flight battery. c. Power ON range extender. d. Power ON FPV device (tablet or smartphone). D. Launch UAS app or Pix4d mapper (FPV Application) application and start to bind it with FPV device (tablet and/or phone). a. Connect to UAS WiFi. b. Wait until rear LED flight indicator lights have ini tialized and is green. c. Check7+ satellites on application. E. Initiate Calibration procedures of UAS compass. a. Calibrate compass (toggle S1 switch 6 times and rate UAS 360 degrees horizontally and vertically). F. Check charging levels for safe flight. G. Setup FPV app for camera/GPS shooting mode. H. Initiate CSC command to start motors. I. Ready to Fly with GPS mode. J. Start Mission K. Hover approximately 10 feet above the ground to confirm UAS is under control. a. Verify all sticks operate correctly while in hover mode. L. Cond uct mission as determined from flight plan. a. Missions are no longer than 15 minutes.ARS Flight Safety and Procedures Manual Rev. 3.13.15 4 

### 4.0 Pre/Post Landing Procedures A. Initiate camera in full up position. B. Stop video recording. C. Check landing zone is secure and safe. D. Land UAS in landing zone. E. Power off with left toggle in down position. a. After UAS has landed, initiate CSC power off with both toggle switches. F. Power Off flight battery. G. Remove battery from UAS. H. Remove props and place within case. I. Power Off remote controller. J. Power Off range extender. K. Power Off FPV device (tablet and/or smartphone). L. Replace gimbal clamp and lens cap. M. Replace UAS, remote controller, and batteries in case.ARS Flight Safety and Procedures Manual Rev. 3.13.15 5 

### 5.0 Equivalent Level of Safety Requirements  All Pilot(s) or PICs must have experience and understanding of how the NAS works and how to communicate with the observers.  To be hired with ARS, all PICs must have a private pilot’s airmen certificate.  All PICs must have 100 hours of training on both the mUAS and sUAS assets.  The flight manual will be with the Pilot or ground station at all times.  The PIC will take all required preflight actions
- including reviewing weather, flight battery requirements, landing and takeoff distance, and aircraft performance data, prior to flight.  Both the Manufacturer Flight Man ual and ARS Flight Safety & Procedures Manual will be located at the ground station with the pilot at all times.  The operator will confirm the altitude of the launch site shown on the GPS altitude indicator before flight.  The PIC will use the GPS altitud e indicator to constantly monitor either the mUAS or the sUAS height, thus ensuring operation at safe altitudes.
 During flight operations, both the mUAS and sUAS will yield right
-of
-way to other aircraft, manned or unmanned.  All flight operations will be i n Class G Airspace.  mUAS flights will be operated at an altitude of no more than 400 feet above ground level (AGL) or no more than 100 feet above a structure being inspected, if that structure exceeds 400 feet.  sUAS flights will be operated at an altitude of no more than 500 feet above ground level (AGL) or no more than 100 feet above a structure being inspected, if that structure exceeds 500 feet.  Flights will be operated at a lateral distance of at least 500 feet from any structure or structure or vehicle unless permission has been granted by the owner or controller of the property in advance of the flight. Flights will not be conducted within 500 feet of any person who is not essential for the conduct of the flight unless that person is in a position whe re they are shielded from the aircraft and any possible debris resulting from an aircraft failure. Flight will be terminated if a person/s breaches safety zone.  At a minimum, the crew for each operation will consist of the Pilot, Visual Camera Observer, Engineer Inspector, and one or more State or local government inspector.  The mUAS pilot will be an FAA licensed airman with a private pilot’s certificate with rotorcraft experience, along with 100 hours of training.ARS Flight Safety and Procedures Manual Rev. 3.13.15 6  The sUAS pilot will be an FAA licensed airman with a private pilot’s certificate with rotorcraft experience along with 100 hours of training.  All Pilots will be vetted by the Transportation Security Administration.  The mUAS Pilot will be trained in flight, operations, and safety procedures in a ccordance with the ARS Flight Safety and Procedures Manual.  Both the mUAS and sUAS Pilots will be Pilot in Command (PIC). If a pilot certificate holder other than the UAS Pilot, who possesses the necessary PIC qualifications, is also present, that person can be designated as PIC.  The mUAS shall not operate in wind gusts greater than 10 mph.  The sUAS shall not operate in wind gusts greater than 18 mph.  Both the mUAS and sUAS will only operate within a confined “Sterile Area”. A sterile area is defined as a safety zone surrounding the subject property that has been cleared of all individuals or animals that aren’t part of the inspection. In addition, the Petitioner shall establish a security perimeter for the flight operations area.  A briefing will be cond ucted in regard to the planned mUAS and sUAS operations prior to each day’s missions. It will be mandatory that all personnel who will be performing duties within the boundaries of the safety perimeter be present for this briefing.  The Pilot, Visual Came ra Observer, and Inspection Engineer will have been trained in operations of UAS generally and will have experience in flying the particular UAS used for any operations.  The Pilot, Visual Camera Observer, Inspection Engineer and State or local inspector w ill at all times be able to communicate by voice or text via cellular or similar device.  All required permissions and permits will be obtained from territorial, state, county or city jurisdictions, including local law enforcement, fire or other appropriate governmental agencies.  The Petitioner will make available to the FAA, upon request, both the mUAS and/or sUAS for inspection or testing, and any associated documents/records required to be kept under the proposed rule.  Report an accident to the FAA withi n 10 days of any operation that results injury or property damage.  If both the mUAS or sUAS loses communications or loses its GPS signal, both assets will have the capability to return to a pre -determined location within the operational area and land.ARS Flight Safety and Procedures Manual Rev. 3.13.15 7  All flight operations will only operate in optimal weather conditions with visibility of at least 3 miles from control station.  Both the mUAS and sUAS will have the capability to abort a flight in case of unpredicted obstacles or emergencies. The Pilot will then safely terminate mission and gain control of UAS and return to a pre
-determine location.  The Petitioner will use a blanket 200-foot Certificate of Waiver or Authorization (COA) for all flights anywhere in the country except in restricted airspace and other areas such as major cities, where the FAA prohibits UAS operations. Moreover, the Petitioner will obtain an Air Traffic Organization (ATO) issued COA for flights above 200 feet prior to conducting any operation under this petition of exemption. 

### 6.0 Specific Operational Procedures for Pilots 6.1 Specific Operational Procedures for Aerial Building Photography & Inspections 1. Ten days before flight operations, the operator will contact the State & local government inspection agency that aerial inspection of vacant or occupied buildings will be occurring. 2. The operator will enforce a safety zone covering 500 feet outside the perimeter of the subject building during flight operations. The safety zone will be established by the operator by using yellow safety tape and the posting of aerial inspection signs (see Supporting Documents). 3. mUAS flights will be operated at an altitude of no more than 200 feet above ground level (AGL). 4. Report an accident to the OSHA and the State & local government agency requesting the inspection within 10 days of any operation that results injury or property damage. 

### 6.2 Specific Operational Procedures for Construction Sites 1. Ten days before flight operations, the operator will contact the State & local government inspection agency t hat aerial inspection of the construction site will be occurring. 2. The operator will enforce a safety zone covering 500 feet outside the perimeter of the construction site during flight operations. The safety zone will be controlled by the general contract or with flaggers and other staff and the posting of aerial inspection flight signs (see Supporting Documents). 3. sUAS flights will be operated at an altitude of no more than 300 feet above ground level (AGL).ARS Flight Safety and Procedures Manual Rev. 3.13.15 8 4. Report an accident to the OSHA and the State & l ocal government agency requesting the inspection within 10 days of any operation that results injury or property damage. 

### 6.3 Specific Operational Procedures for Temporary Tower Crane Assembly Verification Inspections

1. The operator will file a FAA form 77 11- 1, or its equivalent with the local Flight Standards District Office (FSDO). 2. At least five days before schedule inspections, the operator of both the mUAS and sUAS affected by this exemption must submit a written Scope of Work Activities to the local FSDO with jurisdiction over the area of proposed infrastructure inspection. The 5
-day notification may be waived with the concurrence of the FSDO. The Scope of Work includes the following, but not limited to: a. Dates and times of flights. b. Name and phone number of the operator for the UAS inspections conducted under this petition of exem ption. c. Name, phone number, and certificate number of the PIC. d. Make, model, and N - number of UAS asset used in operation.ARS Flight Safety and Procedures Manual Rev. 3.13.15 9 e. A statement that the operator has obtained permission from property owners and/or local officials to conduct the infrastructure inspecti on event; the list of those who gave permission must be made available to the inspector upon request. f. A description of the flight mission, including maps or diagrams of any area, city, town, county, and/or state over which infrastructure inspection will be conducted and the altitudes essential to accomplish the operation. 3. Ten days before flight operations, the operator will contact the State & local government inspection agency that aerial inspection of the tower crane will be occurring on a construction si te. 5. The operator will enforce a safety zone covering 500 feet outside the perimeter of the construction site during flight operations. The safety zone will be controlled by the general contractor with flaggers and the operator will impose a non -fly zone a nd post aerial inspection in progress signs (see Supporting Documents). 4. Both mUAS and sUAS flights will be operated at an altitude of no more than 400 feet above ground level (AGL). 5. Prior to inspection, the general contractor will be required to move the hook (#2) and jib/trolley (#3) in a lock position that provides the best and safe flight path without any obstruction of buildings, people or roadways. 6. The flight operations will be restricted to a spherical flight path surrounding the tower crane startin g with the concrete footing (#11), continuing up the mast (#10

-#7), then moving then horizontally to the counter
-jib ballast (#1), the counter
-jib block (#4), the hoisting drum (#5), continuing past the cabin (#6) and jib
-trolley (#3) and finally to the h ook (#2). Then the operator will repeat the flight path backwards in the following order: #2, #3, #6, #5, #4, #1, #7
-#10, #11, and then land the UAS (see Figure 1). 7. Report an accident to the OSHA and the State & local government agency requesting the insp ection within 10 days of any operation that results injury or property damage.ARS Flight Safety and Procedures Manual Rev. 3.13.15 10 

### 6.4 Specific Operational Procedures for Substructure Bridge Inspections

1. The operator will file a FAA form 7711
- 1, or its equivalent with the local Flight Standards Dist rict Office. 2. Ten days before flight operations, the operator will contact the United States Coast Guard to notify all boaters, military and commercial ship operators that UAS operations are being conducted and to request a Coast Guard Patrol or State/Local Environmenta l Fishery Unit with boat(s) in the water to monitor the safety zone. 3. The operator will conduct only bridge over waterway substructure inspections. 4. A no-fly zone will be established over bridge. 5. UAS flights will be operated underneath the bridge. 6. The operator will conduct a minimum of two missions, all over water, to inspect the bridge substructures using both the mUAS and sUAS assets. 7. Report an accident to the United States Coast Guard within 10 days of any operation that results injury or property damag e. 8. At least five days before scheduled inspections, the operator of both the mUAS and sUAS affected by this exemption must submit a written Scope of Work Activities to the local FSDO with jurisdiction over the area of proposedARS Flight Safety and Procedures Manual Rev. 3.13.15 11 infrastructure inspection. The 5 -day notification may be waived with the concurrence of the FSDO. The Scope of Work includes the following, but not limited to: a. Dates and times of flights. b. Name and phone number of the operator for the UAS inspections conducted under this petition of exemption. c. Name, phone number, and certificate number of the PIC. d. Make, model, and N - number of UAS asset used in operation. e. A statement that the operator has obtained permission from property owners and/or local officials to conduct the infrastructure ins pection event; the list of those who gave permission must be made available to the inspector upon request. f. A description of the flight mission, including maps or diagrams of any area, city, town, county, and/or state over which infrastructure inspection wi ll be conducted and the altitudes essential to accomplish the operation. 

### 6.5 Specific Operational Procedures for the DC Special Flight Rules Area (DC SFRA), including the DC Metropolitan Area Flight Restricted Zone (DC FRZ) 1. Airspace surrounding the Whitehouse, the U.S. Treasury Building, the Mall, and the U.S. Capitol building and grounds are prohibited from flight operations. 2. The operator will notify the U.S. Capitol Police of all flight operations. 3. The Pilot shall review all Notice -To-Airmen (NOTA Ms) and file a DC SFRA Flight Plan with the Washington Flight Standards Office. 4. The Pilot shall communicate with the Washington Flight Standards Office by cell phone stating the current flight operation, location, altitude, and operational timeframe when conducting operations within the DC SFRA, including the DC FRZ. 5. The Pilot shall provide battery level, altitude, and distance from PIC and location for all flight operations to the Washington Flight Standards Office. 6. All flight operations in the District of Columbia will be 350 feet or below. 7. During flight operations, both the mUAS and sUAS will yield right
-of
-way to all military, manned or unmanned aircraft. 8. At least five days before schedule inspections, the operator of both the mUAS and sUAS affected by this exemption must submit a written Scope of Work Activities to the Washington FSDO with jurisdiction over the area of proposed infrastructure inspection. The 5 -day notification may be waived with the concurrence of the FSDO. The Scope of Work includes the following, but not limited to:ARS Flight Safety and Procedures Manual Rev. 3.13.15 12 a. Dates and times of flights. b. Name and phone number of the operator for the UAS inspections conducted under this petition of exemption. c. Name, phone number, and certificate number of the PIC. d. Make, model, and N - number of UAS asset used in operation. e. A statement that the operator has obtained permission from property owners and/or local officials to conduct the infrastructure ins pection event; the list of those who gave permission must be made available to the inspector upon request. f. A description of the flight mission, including maps or diagrams of any area, city, town, county, and/or state over which infrastructure inspection wi ll be conducted and the altitudes essential to accomplish the operation. 9. As part of preflight plans, the Pilot shall review all NOTAMs and file a DC SFRA Flight Plan with the Washington Flight Standards Office. The pilot shall state that “we would like to file a DC SFRA flight plan for a VFR flight at subject property located at ___________________________________________ being inspected.” Next, the operator shall remain only in Class G airspace and request approval to conduct flight operations. During flig ht operations, the operator shall maintain communications with the Washington Flight Standards Office stating current flight operations, location, and altitude. Once flight operations ends, the operator shall notify the Washington Flight Standards Offices by cell phone that flight operations are closed. 10. All Pilots and visual camera operators shall have background checks conducted by the TSA. 11. The Pilot shall engage and maintain contact with the Washington Flight Standards Office by cell phone, without the need for the pilot to monitor VHF frequency 121.5 or UHF frequency 243.0. The Pilot will be notifying the Washington Flight Standards Offices by cell phone of the start and end of flight operations in the DC FRZ and DC SFRA.