Rules (Draft)

We're accepting feedback on these draft rules through Nov. 26, 2025. Send yours by emailing darpaliftchallenge@darpa.mil.

Last updated: Oct. 28, 2025

1.0: General Rules

• 1.1 Eligibility: The competition is open to all teams who have registered for the DARPA Lift Challenge and meet the eligibility requirements.
  • 1.1.1 Registration and participation are limited to individuals who are U.S. citizens or U.S. permanent residents (Green Card holders), representing only U.S. entities (e.g., companies, academic institutions).
  • 1.1.2 To be eligible to win a monetary prize, a team representing an entity (e.g., company or academic institution) must be incorporated and maintain a primary place of business (e.g., located) in the United States. An individual(s) participating singly or in a team not representing an entity, must be a citizen or permanent resident of the United States. The winner will be required to provide a U.S. taxpayer identification number (TIN) or a social security number to receive the monetary prize. Information on how to obtain a TIN is available on the U.S. Internal Revenue Service website at www.IRS.gov.
  • 1.1.3 Registered Team Definition: A registered team is defined as one or more individuals, identified by a Social Security Number (SSN) or Taxpayer Identification Number (TIN).
    • 1.1.3.1 One Aircraft Design Per Team: Each registered team can submit only one aircraft design for evaluation. Teams may bring spare parts or identical copies of their registered aircraft model to the competition.
    • 1.1.3.2 Multiple Designs Require Separate Teams: To submit multiple, distinct aircraft designs, you must register a separate team for each design.
    • 1.1.3.3 No Duplication to Gain Advantage: Teams or groups of teams connected through common members, funding sources, or organizational affiliation may not register multiple teams with the same design concept to gain additional flight windows or other competitive advantages. DARPA reserves the right to disqualify teams found to be in violation of this rule.
• 1.2 Compliance: All participants must comply with these rules, as well as all applicable Federal Aviation Administration (FAA) regulations and safety standards.
• 1.3 Safety: Safety is paramount. Any unsafe behavior or violation of these rules will result in immediate disqualification.
• 1.4 Interpretation: DARPA reserves the right to interpret these rules and make decisions on any matters not specifically covered herein. All DARPA decisions are final.
• 1.5 Amendments: DARPA reserves the right to amend these rules at any time. Any amendments will be communicated, in writing, to all registered participants.
• 1.6 Good Faith: All participants are expected to compete in good faith and to conduct themselves in a sportsmanlike manner.
• 1.7 Disqualification: DARPA reserves the right to immediately disqualify participants from the challenge for violating the rules and/or failing to compete in good faith.

2.0 Aircraft Requirements

• 2.1 Weight Limit: The Unmanned Aircraft System (UAS), including all components (excluding the payload), must weigh less than 55 pounds (24.95 kg) at the time of weigh-in.
• 2.2 Vertical Takeoff and Landing (VTOL): The UAS must be capable of vertical takeoff and landing without the use of runways or launch aids.
• 2.3 Visual Line of Sight (VLOS): All flights must be conducted within visual line of sight of the remote pilot in command (RPIC).
• 2.4 Remote Identification (RID): The UAS must comply with all FAA Remote Identification (RID) requirements.
• 2.5 FAA Compliance: All UAS operations must comply with applicable FAA regulations, including Part 107 (“Small Unmanned Aircraft Systems”), experimental airworthiness, a commercial drone license if desiring to compete for prize money, and any required waivers or exemptions.
• 2.6 Construction: The UAS must be of sound design and construction, capable of safely carrying the specified payload.
• 2.7 Heavier Than Air: The UAS must be a heavier-than-air aircraft. The use of any lighter-than-air gasses to provide lift or to reduce the effective weight of the aircraft is strictly prohibited. If air pressure is used for structural rigidity or pneumatic actuation, it must be atmospheric air, and the individual or team must demonstrate to the satisfaction of the DARPA representative the use of atmospheric air.

3.0 Payload Requirements

• 3.1 Payload Composition: The payload will consist exclusively of standard, commercially available cast iron Olympic barbell gym plates. Acceptable plate weights are: 2.5 lbs, 5 lbs, 10 lbs, 25 lbs, 35 lbs, and 45 lbs. Plates will be circular and of standard dimensions for their weight. The weights for the challenge will be provided by DARPA to ensure uniformity across the competition.
• 3.2 Payload Weight: Teams may attempt flights with any payload weight they choose, up to the maximum capacity of their UAS. The payload weight must be declared prior to weigh-in. 110 lbs is the minimum payload weight to receive a qualifying score.
• 3.3 Plate Combination: The payload must be assembled using the largest plate combinations available. For example, a 30-lb payload must consist of one 25-lb plate and one 5 lb plate (not six 5-lb plates).
• 3.4 Payload Location: All plates comprising the payload must be co-located at a single point on the UAS. Distributed payloads or using the payload as structural reinforcements are not permitted.
• 3.5 Attachment Method: Teams are free to use any method to attach the payload to the UAS (e.g., sling load, direct attachment). However, the attachment method must be secure and must not pose a safety hazard. The attachment method will also be weighed in and will be considered part of the aircraft not payload weight.
• 3.6 No Modifications: The gym plates themselves cannot be modified in any way (e.g., drilling holes, adding attachment points, etc.).

4.0 Flight Requirements

• 4.1 Flight Path: The UAS and payload must take off or be lifted vertically and fly between two points for five nautical miles (5nm), four (4) of these nautical miles will be completed with the payload attached with the last one (1) nautical mile completed without a payload attached.
• 4.2 Flight Altitude: The UAS must maintain a consistent altitude of 350 feet (+/- 50 ft) (121.92 meters) above ground level (AGL) throughout the flight. Ascent to and descent from cruising altitude must be made in a reasonable time. Once 350 ft is obtained, the aircraft will have to maintain that +/- 50 ft until a verbally declared descent.
• 4.3 Visual Line of Sight (VLOS): The UAS must remain within visual line of sight of the RPIC at all times. If any form of autonomous flight control is used, a safety pilot in command must be used and have the ability to take over control of the UAS at any time during the course.
• 4.4 Take Off: The aircraft may take off separately from the payload if desired. Time will start when the payload lifts off the ground. Take off must not be assisted by any ground support equipment. The aircraft must be “self-sufficient” (no launch stands, power tethers etc.).
• 4.5 Dropoff and Landing: After four (4) nautical miles of flight, the aircraft will return its payload to the landing zone. The payload release can be human or mechanical. The payload must touch the ground prior to being released and be in a controlled manner (no airdropping or excessive speed). After completing the last unloaded mile, the UAS must land vertically in a controlled manner within the designated landing zone. The landing zone will be a circle with a radius of 10 feet (3.05 meters). (the intent is for the aircraft to land inside the circle to show a controlled landing, not as a design restraint) If the UAS requires any repairs, beyond basic safety checks, prior to being capable of flying again, the landing will not be considered successful.
• 4.6 Flight Time: The course flight time must be under 30 minutes. The clock starts with payload lift off and ends with the aircraft safely landing in the designated zone and the power being cut.
• 4.7 Attempts: Each team will have two 90-minute windows, each on separate days to post their best score. If a team makes a mistake on a particular run, they can immediately return to the start to attempt another run if time allows. The lane coordinator will attempt to notify the team at the time of the infraction, but post analysis may also uncover an infraction that could invalidate a particular run. The lane coordinator may also call a stop to a particular run due to safety concern. If the incident was the team’s fault, any time lost during the adjudication will be forfeited. If the safety concern was external, the lane coordinator will attempt to give that time back if the opportunity presents itself. If the team would like to appeal the lane coordinator’s determination, DARPA will be the deciding authority.
• 4.8 Evaluation Weather Conditions: Flight attempts will be conducted during daylight hours and in weather conditions deemed safe by the DARPA representative. No flights will be started in precipitation, or winds exceeding 25 knots steady or gusting. If weather goes out of limits during a flight it will be up to the lane coordinator to assess the risk and the time left for the competitor to complete the run. If there is a quick light rain or a momentary spike in winds during an event that did not significantly affect the outcome of the run, the run will be counted and the team will not be given additional time. If the team would like to appeal the lane coordinator’s determination, DARPA will be the deciding authority.

5.0 Weigh-In and Verification

• 5.1 Weigh-In Procedure: The UAS and payload will be weighed by the DARPA representative immediately prior to each flight attempt. The weight will be measured using a certified scale.
• 5.2 Payload Verification: The DARPA representative will verify that the payload consists of approved gym plates and meets all payload requirements outlined in Section 3.0.
• 5.3 Tracker Installation: A Government-provided tracking device will be securely attached to the payload prior to each flight and will be calculated as payload weight. The FAA required Remote ID will also be used to track the aircraft when it does not have the payload attached.

6.0 Scoring

• 6.1 Primary Metric: The primary metric is the maximum payload weight divided by the aircraft weight successfully carried over the flight course outlined in Section 4.0.
• 6.2 Tiebreaker: In the event of a tie, the team with the highest payload weight will be declared the winner. If a tie persists, the team with the fastest time will be declared the winner.

7.0 Data Collection

• 7.1 Tracking Data: The Government-provided tracking device will record airspeed, altitude, location, path, and total distance traveled. This data will be used to verify compliance with the flight path requirements. Tracking data will be displayed in front of the pilot and will be tracked by software that will notify the pilot of any course rule infraction(s).
• 7.2 Flight Logs: Teams must maintain a detailed flight log for each flight attempt, including the payload weight, flight time, energy usage, and any other relevant information.

8.0 Flight Scheduling and Window Selection

• 8.1 Flight Window Selection: Teams will be assigned their preferred flight windows based on registration date and time (early registration will receive seniority for selecting flight windows).
• 8.2 Flight Windows: Each team will be assigned two (2) 90-minute flight windows during the evaluation period.
• 8.3 Flight Attempts: Teams may attempt as many successful runs during their flight window as possible. The highest score of the flight window will be submitted for review at the end of each flight window. The highest overall score for a team will be maintained throughout the competition.
• 8.4 Scheduling Changes: The flight schedule is subject to change due to unforeseen circumstances, such as teams dropping out of the competition or UAS crashes during testing. DARPA will make every effort to accommodate teams and provide reasonable notice of any scheduling changes.
• 8.5 Missed Flight Window: If a team is unable to fly during their scheduled flight window, they may forfeit their attempts. DARPA may, at its discretion, offer an alternate flight window, but this is not guaranteed. Team check-in will be required within 15 minutes of event window start time.
• 8.6 Rescheduling: Teams may contact DARPA to reschedule their window if they have a valid reason. DARPA will attempt to accommodate the request.

9.0 Safety Requirements

• 9.1 Remote Pilot in Command (RPIC): Each team must designate a RPIC who holds a valid FAA Part 107 remote pilot certificate and must provide proof of a valid FAA Part 107 remote pilot certificate to the DARPA representative prior to flight.
• 9.2 Visual Observer (VO): Each team must designate a VO to assist the RPIC in maintaining visual line of sight with the UAS.
• 9.3 Pre-Flight Inspection: The RPIC must conduct a thorough pre-flight inspection of the UAS to ensure that it is in safe operating condition.
• 9.4 Emergency Procedures: Teams must have established emergency procedures in place in the event of a UAS malfunction or another unforeseen event.