This SOP defines the field operating procedure for RPAS / drone missions performed by 33Visual along the Atizapán–Atlacomulco highway corridor for Concesionaria AT-AT, S.A. de C.V., subsidiary of Aleatica, S.A.B. de C.V.

• Support safe, documented and repeatable drone operations.
• Maintain clear coordination between 33Visual, Aleatica / AT-AT and field personnel.
• Establish a consistent workflow for mission preparation, flight execution and post-flight closeout.

• Pilot in command: Responsible for flight safety, mission execution, pre-flight review, aircraft control and go / no-go decisions.
• Visual observer: Maintains awareness of the drone, obstacles, people, vehicles, construction activity and manned aircraft.
• Field support / safety contact: Supports launch zone control, local coordination, access, road safety and emergency communication.
• Client / site contact: Confirms access, workfront conditions, site restrictions and local coordination requirements.

• Confirm mission objective, segment, date, pilot, observer, aircraft and planned maximum altitude.
• Review the flight map, terrain, access points, takeoff / landing areas and expected line of sight.
• Confirm batteries, controller, payload, memory cards, PPE, field kit and data capture requirements.
• Confirm emergency contact, client / site contact and communication method before mobilizing.

• Review nearby aerodromes, heliports, planning radii and any relevant operational constraints before each mission.
• Review NOTAMs and current aeronautical information before flight.
• Coordinate with the client / site contact and relevant project personnel before operating in the selected segment.
• Do not fly if airspace, weather, access or safety conditions are not acceptable for the planned operation.

• Check in with the client / site contact before beginning field activity.
• Review workfront conditions, active construction, traffic, machinery, restricted areas and public exposure.
• Conduct a short crew briefing covering mission objective, roles, hazards, emergency actions and communication.
• Confirm that all required PPE and field safety requirements are in place.

• Select a stable takeoff / landing zone away from active traffic, people, machinery and loose debris.
• Maintain control of the launch zone during takeoff, landing and battery changes.
• Identify an emergency landing area before launch.
• Pause launch or landing if people, vehicles or equipment enter the immediate operating area.

• Maintain visual line of sight, VLOS, during the operation.
• Use the visual observer to monitor the drone, airspace, obstacles, traffic, people and workfront activity.
• Maintain the planned altitude and respect any lower restriction that applies to the segment.
• Segment the mission if the corridor length, terrain or line of sight does not support a single safe operation.

• Do not operate in a way that distracts drivers, exposes uninvolved people or interferes with construction activity.
• Avoid unnecessary hovering over active traffic or public areas.
• Maintain a conservative buffer from vehicles, workers, equipment, bridges, power lines and other structures.
• Coordinate with the local team when working near active lanes, closures, toll areas, bridges, tunnels or heavy equipment.

• Terminate or pause flight if manned aircraft activity, unsafe weather, loss of VLOS, public exposure or site conflict is observed.
• If control link is degraded, follow the aircraft emergency procedure and maintain awareness of the return path.
• If an incident occurs, secure the area, notify the client / site contact and document the event.
• Record anomalies, incomplete coverage, equipment issues or safety concerns in the field notes.

• Inspect the aircraft, payload, batteries and equipment after landing.
• Confirm that flight logs, imagery, mapping data and field notes are saved.
• Back up captured data according to 33Visual data handling procedures.
• Notify the client / site contact that the field operation has concluded.