Raytheon Coyote is a compact fixed-wing military\/tactical drone aimed at defense, institutional, and research-oriented readers rather than consumer pilots. It matters because it combines a relatively small 6.4 kg maximum takeoff weight with a notably brisk 157 km\/h top speed, giving it a different profile from slower multirotor systems and larger long-endurance tactical UAVs. Publicly confirmed buyer-facing details are limited, so this page focuses on what is known, what can be reasonably inferred, and what still needs verification.<\/p>\n\n\n\n
Unlike consumer drones that are sold on camera specs, app features, and price transparency, the Coyote sits in a category where the most important information is often operational, contractual, or variant-specific. That makes it harder to summarize in the usual \u201cbuy or skip\u201d format. Still, it remains a useful reference point because it represents a compact fixed-wing platform with defense relevance, and because the available headline figures suggest a fast, relatively lightweight aircraft for short-duration tactical work.<\/p>\n\n\n\n
This article is therefore best read as a structured reference for analysts, researchers, procurement teams, journalists, and technically curious readers who want a grounded overview without assuming details that are not publicly confirmed. Where hard data exists, it is presented directly. Where information is missing, that uncertainty is treated as part of the evaluation rather than glossed over.<\/p>\n\n\n\n
The Raytheon Coyote is an active U.S.-origin fixed-wing military\/tactical drone from Raytheon. For readers comparing defense-linked unmanned platforms, it stands out less for consumer-style feature lists and more for its compact dimensions, respectable speed, and continued relevance in an active program context. That said, the publicly confirmed specification set is much thinner than what you would expect from a commercial drone listing, so careful version-by-version verification is essential.<\/p>\n\n\n\n
That lack of public detail is not unusual in the defense and institutional UAV world. Consumer products typically advertise everything from obstacle sensing to codec support because retail buyers expect easy comparison. Defense systems are different. Public descriptions may emphasize only a few broad performance metrics, while payload packages, communications architecture, operating concepts, software stack, sustainment support, and procurement terms are left to official briefings, contracts, or restricted documentation. As a result, any article on a platform like Coyote has to balance useful interpretation with caution.<\/p>\n\n\n\n
Another reason the Coyote attracts attention is that it occupies an interesting middle space in the unmanned market. It is much smaller than many higher-end tactical ISR platforms, but it is also more purposeful and performance-oriented than lightweight civilian fixed-wing drones. That makes it relevant when discussing tactical mobility, compact field deployment, rapid-response missions, and situations where hovering is less important than forward-flight efficiency and speed.<\/p>\n\n\n\n
For anyone encountering the name for the first time, the most important takeaway is that Coyote should be treated as a program family reference point, not a neat consumer product with one stable spec sheet and one fixed accessory list. Serious evaluation depends on identifying the exact configuration under discussion.<\/p>\n\n\n\n
Coyote is a fixed-wing tactical UAV from Raytheon, built in the USA and listed as active. The supplied record confirms a 6.4 kg maximum takeoff weight, 1.5-hour endurance, 32 km range, 157 km\/h maximum speed, 6,096 m ceiling, 1.5 m wingspan, and 0.9 m length.<\/p>\n\n\n\n
Those numbers describe a compact aircraft with a strong emphasis on forward-flight performance rather than stationary hovering. In simple terms, this is the kind of platform you evaluate for tactical movement, coverage, and mission-specific airborne utility, not for close-range cinematic flying or simple point-and-shoot operations. Fixed-wing UAVs in this size class usually trade hover capability for speed, aerodynamic efficiency, and broader area access, and Coyote appears to fit that general pattern.<\/p>\n\n\n\n
The basic dimensions also matter more than they might at first glance. A 1.5 m wingspan and 0.9 m length place the aircraft firmly in the compact tactical bracket rather than the larger fielded endurance class. That influences transport, launch planning, training burden, and likely mission design. It also hints at a system that may be easier to move and stage than heavier runway-dependent aircraft, although the exact launch and recovery concept still needs confirmation.<\/p>\n\n\n\n
This is not a typical retail drone. The most relevant audience is defense procurement teams, institutional evaluators, researchers, analysts, and journalists comparing small tactical fixed-wing systems. It is far less relevant to hobby pilots, photographers, or small commercial operators looking for turnkey civilian workflows.<\/p>\n\n\n\n
A practical way to think about the target audience is to ask who can actually act on incomplete but operationally meaningful information. A consumer buyer usually needs transparent pricing, a dealer network, compatible accessories, camera results, app screenshots, and clear legal use cases. A defense or institutional evaluator can work from a narrower public baseline because they may have access to formal channels, briefings, test opportunities, or procurement documentation. That distinction is central to how a system like Coyote should be assessed.<\/p>\n\n\n\n
It may also be relevant to academic and policy researchers studying the evolution of compact unmanned systems, especially where the line between reconnaissance, tactical utility, and broader defense integration is important. In that context, Coyote is useful not because every detail is publicly visible, but because it illustrates how compact fixed-wing systems can be positioned differently from both quadcopters and larger surveillance UAVs.<\/p>\n\n\n\n
Its main differentiator is the combination of compact size and relatively high speed in a small tactical fixed-wing format. It also sits in a category where public information is often fragmented across variants, making Coyote more of a program-family reference point than a simple off-the-shelf shopping decision.<\/p>\n\n\n\n
Many small drones are easy to classify. Consumer quadcopters are built around cameras and ease of use. Large tactical fixed-wing UAVs are built around endurance and sensor persistence. Coyote appears to occupy a more specialized position: small enough to remain relatively compact, but fast enough to suggest a more dynamic mission envelope than slower observation-centric systems.<\/p>\n\n\n\n
That matters because speed changes what a drone can do well. It can reduce transit time to an area of interest, alter response options, and reshape the tradeoff between persistence and agility. A platform that is compact and fast may be attractive where rapid tactical deployment matters more than staying airborne all day. Even without a fully confirmed public payload picture, that speed-to-size profile is one of the clearest reasons Coyote remains a notable reference point.<\/p>\n\n\n\n
The feature list above is intentionally conservative. It includes the key metrics that are confirmed while leaving out assumptions that are common in civilian reviews but unsupported here. That approach is important because many readers instinctively expect a drone review to name the camera, the obstacle sensors, the control app, supported flight modes, and charging ecosystem. In Coyote\u2019s case, those details are either variant-dependent or not publicly confirmed in the supplied record.<\/p>\n\n\n\n
Even so, the confirmed numbers tell us a lot. A 6.4 kg maximum takeoff weight paired with 157 km\/h top speed suggests a platform that is not ultra-light, but still compact enough to fall below the larger tactical UAV classes that require more logistics and support infrastructure. A 1.5-hour endurance places it in a useful tactical bracket, though not in the long-loiter category. And the 6,096 m service ceiling indicates substantial altitude headroom on paper, even if actual operations would depend heavily on mission rules, launch conditions, and airspace control.<\/p>\n\n\n\n
| Specification<\/th>\n | Details<\/th>\n<\/tr>\n<\/thead>\n | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Brand<\/td>\n | Raytheon<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Model<\/td>\n | Coyote<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Drone Type<\/td>\n | Fixed-wing<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Country of Origin<\/td>\n | USA<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Manufacturer<\/td>\n | Raytheon<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Year Introduced<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Status<\/td>\n | Active<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Use Case<\/td>\n | military\/tactical<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Weight<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Dimensions (folded\/unfolded)<\/td>\n | Length 0.9 m; wingspan 1.5 m; folded dimensions not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Max Takeoff Weight<\/td>\n | 6.4 kg<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Battery Type<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Battery Capacity<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Flight Time<\/td>\n | 1.5 hr<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Charging Time<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Max Range<\/td>\n | 32 km<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Transmission System<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Top Speed<\/td>\n | 157 km\/h<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Wind Resistance<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Navigation System<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Obstacle Avoidance<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Camera Resolution<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Video Resolution<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Frame Rates<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Sensor Size<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Gimbal<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Zoom<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Storage<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Controller Type<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| App Support<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Autonomous Modes<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Payload Capacity<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Operating Temperature<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Water Resistance<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Noise Level<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Remote ID Support<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Geo-fencing<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Certifications<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| MSRP \/ Launch Price<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Current Price<\/td>\n | Not publicly confirmed in supplied data<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Service Ceiling<\/td>\n | 6,096 m<\/td>\n<\/tr>\n | ||||||||||||||||||||||||||||||||
| Airframe Type<\/td>\n | Fixed-wing<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n The table is useful as a snapshot, but it should not be mistaken for a complete procurement document. In a consumer review, empty fields often imply weak product support or poor transparency. In a defense context, they more often reflect the fact that many details are not distributed in public marketing form. That means the absence of data is not itself a condemnation of the system, but it does limit what outside observers can responsibly conclude.<\/p>\n\n\n\n It is also worth noticing which metrics are present. The public record emphasizes core air vehicle performance: weight class, endurance, speed, range, dimensions, and ceiling. These are the broad figures most relevant when positioning a drone within the tactical fixed-wing landscape. By contrast, buyer-experience details\u2014charging times, software compatibility, image pipeline, repair turnaround, and accessory ecosystem\u2014remain unknown here.<\/p>\n\n\n\n For institutional readers, that creates a useful screening framework. The confirmed specifications are enough to say Coyote belongs on a shortlist for compact tactical fixed-wing comparison. They are not enough to support a final acquisition decision without direct follow-up.<\/p>\n\n\n\n Design and Build Quality<\/h2>\n\n\n\nBased on the confirmed dimensions, Coyote is compact for a tactical fixed-wing platform. A 1.5 m wingspan and 0.9 m length put it well below the size of larger persistent-surveillance UAVs, while the 6.4 kg maximum takeoff weight suggests a more substantial airframe than a hobby foam plane or lightweight consumer system.<\/p>\n\n\n\n That size-to-weight relationship is significant. A platform at this scale can be described as compact, but not disposable in the casual sense. It is large enough to imply a serious tactical role, serious support requirements, and likely a more robust design philosophy than hobby-oriented aircraft. In other words, this is not merely a small plane with a radio link. It is a fielded system concept intended for institutional use.<\/p>\n\n\n\n Material composition, foldability, and ruggedization details are not publicly confirmed in the supplied data. Still, because this sits in the military\/tactical segment, it is reasonable to expect field-readiness to matter more than convenience-focused consumer design. In practical terms, that usually means transportability, maintainability, and mission packaging are more important than portability in the backpack-drone sense.<\/p>\n\n\n\n That distinction matters because \u201cportable\u201d means different things in different markets. For a consumer, portable often means under-seat travel, rapid unfolding, and quick battery swaps from a shoulder bag. For a tactical system, portable may instead refer to whether the aircraft, launch equipment, ground-control elements, and mission accessories can be moved by a small team and set up under operational constraints. Without confirmed launch-and-recovery details, it is hard to define the exact deployment burden, but the airframe dimensions at least suggest that Coyote avoids the footprint associated with much larger runway-oriented UAVs.<\/p>\n\n\n\n Launch and recovery method are not confirmed here, which is important because that can significantly affect deployment footprint and operator workload. Serviceability and spare-parts architecture are also not publicly detailed in the supplied record.<\/p>\n\n\n\n Those missing details are more important than they first appear. A compact aircraft can still require a fairly involved support setup if launch equipment, retrieval hardware, or mission-specific accessories are specialized. Conversely, a modestly larger aircraft can be easier to manage if its field process is mature and standardized. For real-world procurement, the design question is never just \u201cHow big is it?\u201d but \u201cHow many people, how much gear, how much training, and how much time does one mission cycle actually require?\u201d<\/p>\n\n\n\n Flight Performance<\/h2>\n\n\n\nThe confirmed numbers suggest a drone that prioritizes short-to-medium duration tactical missions over long stationary persistence. A 1.5-hour endurance is useful, but it does not place Coyote in the same class as larger fixed-wing ISR aircraft built for many hours aloft.<\/p>\n\n\n\n That said, 1.5 hours is not trivial. In tactical environments, that duration can still support meaningful transit, observation, response, or target-area access depending on how the mission is structured. The limitation is not that the endurance is poor in absolute terms, but that it shapes the mission toward shorter windows and more deliberate energy management than a long-loiter platform would require. Operators evaluating Coyote would likely care about how much of that 1.5-hour figure remains after launch, climb, transit, maneuvering, reserve planning, and recovery.<\/p>\n\n\n\n Where Coyote looks strong on paper is speed. A 157 km\/h maximum speed is notably brisk for a small UAV and indicates a platform that can cover ground faster than most multirotors and many smaller fixed-wing observation drones. That does not automatically mean better real-world mission performance, but it does suggest a more dynamic flight profile.<\/p>\n\n\n\n Speed matters in several ways. First, it can reduce time-to-station, which may be important in a tactical scenario where the value of information drops quickly with delay. Second, it can improve responsiveness when a system must reposition, intercept, or move between areas of interest. Third, speed often influences survivability and mission flexibility, though those effects depend on the broader operational context and cannot be assumed from top speed alone.<\/p>\n\n\n\n It is also important to interpret \u201ctop speed\u201d carefully. Maximum speed is rarely the same as efficient cruise speed, and sustained high-speed operation can reduce endurance. Without public data on cruise performance, loiter speed, or power system characteristics, we should avoid over-reading the 157 km\/h figure. Even so, it remains one of Coyote\u2019s standout public metrics because it clearly separates the platform from slower systems that are optimized primarily for steady observation rather than tactical movement.<\/p>\n\n\n\n The 32 km range points to a relatively short-range tactical role rather than a long-distance strategic one. The 6,096 m ceiling is also significant; while actual operating altitude depends on mission rules and airspace constraints, the paper ceiling gives it a generous altitude envelope for a compact airframe.<\/p>\n\n\n\n Range figures should be treated with the same caution as endurance and speed figures. \u201cRange\u201d can refer to different things in different documents: a communications limit, a mission radius, a point-to-point operating distance, or a practical operational figure under ideal conditions. Because the supplied data provides the number but not the exact methodology, the 32 km value is best used as a comparative indicator rather than a guarantee of all-condition operating reach.<\/p>\n\n\n\n The 6,096 m service ceiling deserves similar nuance. A high ceiling on paper does not mean the system will routinely operate anywhere near that altitude. Operational ceilings are constrained by payload effectiveness, weather, launch conditions, airspace rules, and mission purpose. Still, ceiling is a meaningful indicator of airframe and propulsion capability, and for a compact system, 6,096 m is an attention-grabbing number.<\/p>\n\n\n\n Wind resistance, signal resilience, and takeoff\/landing behavior are not publicly confirmed in the supplied data. As analysis, fixed-wing aircraft of this size are often more efficient in forward flight than multirotors, but they are also less flexible in confined areas and are not realistic indoor platforms.<\/p>\n\n\n\n This is one of the core tradeoffs any evaluator should keep in mind. A fixed-wing drone can offer better aerodynamic efficiency and faster transit, but it usually demands more planning around launch, recovery, and airspace. That means Coyote likely makes the most sense in environments where those tradeoffs are acceptable and where hover is not the main operational requirement.<\/p>\n\n\n\n Camera \/ Payload Performance<\/h2>\n\n\n\nThis is not a consumer camera drone listing, and the supplied data does not confirm any specific camera, gimbal, sensor size, video specification, or payload capacity. That means buyers should not assume a standard imaging package.<\/p>\n\n\n\n This point is worth stressing because many drone readers instinctively look for a headline camera specification as a proxy for overall usefulness. That logic works reasonably well in the consumer market. It works poorly in the tactical market. Military and institutional UAVs are often evaluated first by mission compatibility, data-link integration, target utility, and payload interchangeability rather than by single-sensor image quality alone.<\/p>\n\n\n\n For a military\/tactical platform, payload value is usually defined by mission fit rather than cinematic quality. If Coyote is being evaluated for observation, test, or broader institutional roles, the most important questions are the exact sensor package, stabilization quality, data-link integration, and how the payload output fits the user workflow.<\/p>\n\n\n\n That workflow dimension is especially important. A payload can be technically capable yet operationally awkward if the ground segment, transmission format, display tools, or downstream analytics are weak. Conversely, a modest sensor can become highly useful if it is tightly integrated into a command-and-control or research pipeline. Since none of those elements are confirmed in the supplied data, the correct approach is to treat payload performance as an open question tied to the exact configuration.<\/p>\n\n\n\n It is also worth being cautious with the model name itself. Public reporting has discussed more than one Coyote-related configuration over time, so exact payload assumptions should be tied to the precise variant under consideration, not the family name alone.<\/p>\n\n\n\n That family-name issue is probably one of the biggest sources of confusion for outside readers. If a drone name appears across multiple news stories, test programs, or contract mentions, it is easy to treat all descriptions as describing the same aircraft in the same form. In practice, defense programs often evolve over time, and the same umbrella name may cover different blocks, payloads, or mission kits. For Coyote, that means even well-intentioned public research can blur important distinctions unless the exact variant is pinned down.<\/p>\n\n\n\n For analysts and prospective institutional users, the key payload questions to verify directly are straightforward:<\/p>\n\n\n\n
|