MAV Operations
Overview:
Phases of MAV operations include launch, enroute, hover, perch, landing, recovery and out of bounds. MAVs may also be landed to disarm mines and may be engaged by the red team while in hovering flight.
Launch: MAVs can be launched from the VTOL launch points, the FW runway in the vicinity of the ground control station (GCS) and from a team UGV. MAVs cannot be launched from the team UGV until the UGV has moved to the north of the VTOL launch point. Prior to first launch, teams must accomplish a number of tasks:
- Safety brief complete – Go
- Flight termination procedure demonstrate (on ground) - Go
- Brief established order of MAV launch (teams with multiple MAVs) – Go (*)
- Brief direction of takeoff and location of the “fly home” lost link point for MAV – Go (*)
- Frequency checks (Confirm all transmitting frequencies with spectrum analyzer) – Go (*)
- Commo checks with all safety pilots (voice and RC control) – Go (*)
- Verify all system/team specific checks or judges requested parameters – Go (*)
- Wind/Wx Check – Go (*)
- Safety Officer/Judges Ready (Position/Commo) – Go (*)
- Acoustic/Red Team/Test Support Team/Photo Team Ready – Go (*)
- Sim UGV/Commando Ready - Go
- Receive airspace/range clearance from the range safety officer – Go (*)
- Mission Director – Go (*)
(*) Required for subsequent MAV launches
Enroute:
During the enroute phase, MAVs can maneuver as desired within the limits of their flight envelopes and the flight rules for the MAV 08 demonstration. All operations outside normal procedures or parameters should be announced to the judges and mission director. Teams should follow their emergency procedures and the test team will work to provide support to ensure the safety of personnel and integrity of the MAV.
Hover:
In the hover mode, MAVs are vulnerable to engagement by the red team. When a member of the red team points to a stationary MAV and announces it to the judge, if the judge determines that the MAV appeared stationary relative to his position the judge will announce that the MAV has been successfully engaged by the red team. MAVs that have been engaged by the red team must cease mission operations, land and are no longer able to participate in the demonstration.
Landing:
VTOL MAVs may land on the surface of the DZ anywhere within the no fly boundary. There are 4 approved landing site for MAVs on top of buildings in the area around the hostage building.
Perch:
MAVs are vulnerable to detection and engagement by the red team if they slow to a hover during the approach to a perch. Approach to the perch site should be carried out at airspeeds less than 20 knots ground speed below 100 ft AGL. Approach to the perch sites should be accomplished while the line of sight to the red team guards is blocked by the hostage building, trees or roof structures.
Recovery:
MAVs will be left on the ground, landing pad or rooftop where they land until completion of the demonstration. Teams are responsible to quickly dispatch a recovery team to ensure all MAVs are cleared form the range within 10 minutes after end of mission. The organizers will provide transportation and ladders to facilitate access to the landing points.
MAVs Beyond the No-Fly:
MAVs that depart the fly out boundary will be followed by a vehicle until termination. The lost MAV team will recover the MAV components as able and return them to the team. Team with MAVs that do not terminate as directed after passing beyond the No-Fly Boundary will immediately stop work on the mission and work to support the lost MAV chase team in the recovery effort.
Cancelling Red Team Participation:
If a team determines that they are unable to make any further progress on the mission scenario due to MAV/UGV/Commando losses, the team may elect to continue the MAV demonstration without red team participation. Mission tasks performed during this situation do not count toward the Best Mission Performance award but will be observed by the judges until the 40 minute demonstration block is complete.