First Breach (NASDAQ: FBDT) says its proprietary quadcopter has flown a mission entirely on its own. In an October 13 announcement, the Hagerstown, Maryland defense company said the prototype took off, followed a predetermined route using satellite navigation, returned and landed with no manual control input from a pilot. I would argue the quiet part of that sentence is the important one: nobody touched the sticks.
To see why, split flying into three jobs. Navigation answers where the aircraft is. Guidance decides where it should go next. Control works out what each of the four motors should do right now to get there. A pilot with a transmitter does the first two in their head and hands the third to the flight controller. First Breach says this flight validated the full autonomy loop of guidance, navigation and control on the current prototype, which means all three ran on board, continuously, from takeoff to touchdown. "Untethered flight showed we had a vehicle. Autonomous flight shows we have a system," said Jeffrey Low, co-founder and chief executive. "The aircraft was given a mission and it executed that mission on its own, from takeoff to landing."
The progression is worth laying out, because it came quickly. The company announced that it had completed its first flight in late August, as this magazine reported at the time. On September 23 it followed with its first untethered flight, a milestone that showed the airframe and motors could hold the aircraft up on their own. This announcement is the third step. Brett Phillips, chief revenue officer of Hellbender, the engineering partner behind the program, called them "three milestones in a matter of weeks, each one building on the last." Read in order, they describe a vehicle, then a free-flying vehicle, then a vehicle that can be given a job.
One detail from the September flight still matters. That aircraft flew on commercial flight electronics, not on the controller First Breach and Hellbender developed, and the next step was to put the two together. The new release says the autonomous mission was flown on Betaflight, the open-source flight control firmware on which the company’s flight controller was first brought up. It does not say whether the aircraft carried that in-house controller or the commercial electronics used in September. That is the question I would ask first, because it decides whether this milestone also closes the integration gap flagged last month.
Betaflight is best known on first-person-view racing and freestyle drones, where it is tuned to make an aircraft feel responsive under a human pilot. The next move is to PX4, an open-source autopilot widely used across defense, industrial and research unmanned systems. The company says it is now porting its flight stack to PX4, and that the port is in process and runs in parallel with airframe and electronics iteration. The reason is mission logic. PX4’s mission planning, failsafe and sensor integration framework is the foundation, in the company’s words, for more complex mission profiles and payload behaviors. A failsafe is what the aircraft does when something goes wrong, such as losing its control link or running low on battery, and for a military customer that behavior is as important as how well the drone flies on a good day. My read is that Betaflight got First Breach to a flying, autonomous aircraft quickly, and PX4 is where it plans to build the one it sells. The cost is that the autonomy has to be proven again on the new software.
The prototype itself is still a proof of concept, and the company says its specifications may change before production. It is a four-rotor Class 1 platform with an all-up weight of about 2.2 kg and a payload capacity of roughly 500 g through a Picatinny rail, the standard accessory rail on military rifles, and an electrical interface. First Breach lists an effective range of 2 km, endurance of about 10 minutes, a cruise speed of 50 km/h and a top speed of 120 km/h. Navigation is GNSS with visual-inertial augmentation, the control link is 900 MHz MAVLink, the batteries are swappable LiPo packs, and the aircraft is designed for field assembly in under ten minutes. By my arithmetic, a 2 km out-and-back is about 4 km of flying, roughly five minutes at cruise speed, which would leave about half the battery as margin on a 10-minute pack. That is a short-sortie aircraft, consistent with the small, low-cost drones that militaries now buy by the thousand.
The manufacturing timeline has not moved. First Breach still targets completing its initial prototypes in the fourth quarter of 2026 and starting scaled production in the second quarter of 2027, with a targeted capacity of more than 2,500 drones a week as manufacturing operations expand. Over a year that would be about 130,000 aircraft, a figure that depends entirely on the prototypes being finished and the factory being ready. As reported earlier, the company holds more than 200,000 contiguous square feet in Hagerstown for drone production and robotic assembly, alongside its ammunition lines.
What the announcement does not contain is data. There is no distance flown, flight duration, altitude, wind condition, route length or number of flights, so the mission is described but not measured. The release photo is captioned as a prototype in flight with a payload, yet the text gives no payload mass or type. The route was flown by satellite navigation, and the visual-inertial augmentation in the specification list is not described as part of the test, so the aircraft’s behavior when satellite signals are degraded is still unreported. The next checkpoint worth watching is straightforward: the same mission flown on PX4, on the in-house controller, with a payload. The harder question is whether the fourth-quarter prototypes arrive on schedule.
Leave a Reply