The Hacker HAES 90 is a Czech fixed-wing commercial\/utility drone aimed at operators who need efficient forward-flight coverage rather than multirotor hovering. Based on the limited confirmed public data available, it offers 1 hour of endurance, 10 km range, a 90 km\/h top speed, and a 2.4 m wingspan. That puts it on the radar for readers comparing survey, monitoring, and general enterprise UAV platforms, especially where fixed-wing efficiency matters more than vertical takeoff convenience. At the same time, many of the details that normally drive a real buying decision still need direct vendor confirmation, so this is best read as a careful market overview rather than a fully verified hands-on recommendation.<\/p>\n\n\n\n
Best For:<\/strong> Enterprise users evaluating fixed-wing platforms for area coverage, monitoring, and payload-dependent utility missions<\/li>\n
Price Range:<\/strong> Not publicly confirmed in supplied data<\/li>\n
Launch Year:<\/strong> Not publicly confirmed in supplied data<\/li>\n
Availability:<\/strong> Not publicly confirmed in supplied data<\/li>\n
Current Status:<\/strong> Unknown<\/li>\n
Overall Rating:<\/strong> Not rated due to limited confirmed data<\/li>\n
Our Verdict:<\/strong> A potentially useful fixed-wing utility platform with solid headline flight figures, but too many core details remain unconfirmed to recommend without direct manufacturer or dealer verification.<\/li>\n<\/ul>\n\n\n\n
If you only need the shortest take: the HAES 90 looks interesting on basic flight metrics, but it remains a due-diligence drone rather than a straightforward buy. The airframe class makes sense for field coverage work, yet the lack of public payload, software, support, and pricing details is too significant to ignore.<\/p>\n\n\n\n
Introduction<\/h2>\n\n\n\n
The HAES 90 is listed as a fixed-wing commercial\/utility drone from Hacker, a Czech manufacturer and brand. Publicly visible structured data confirms a small set of core flight metrics, but not the deeper details buyers usually need, such as payload options, weight, software stack, support network, regulatory class, or pricing. That matters because enterprise UAV procurement is rarely driven by headline endurance alone. In real-world operations, teams also need to know how the aircraft launches, how it recovers, what sensors it supports, how quickly it can be repaired, and whether its software integrates with existing workflows.<\/p>\n\n\n\n
For that reason, this model matters most to readers building a shortlist of enterprise UAVs rather than shoppers expecting a fully documented retail drone. It may also be relevant to researchers, integrators, and fleet managers looking beyond the most visible global drone brands. In many markets, smaller or regional manufacturers can offer practical airframes with competitive mission performance, but the tradeoff is often documentation depth and ecosystem maturity.<\/p>\n\n\n\n
That is the central issue with the HAES 90. The available information suggests a serious field aircraft rather than a consumer gadget, yet the public record is not complete enough to judge it in the same way you would assess a mainstream enterprise drone with a published brochure, payload matrix, supported software list, and clear after-sales support path. So the right way to approach this aircraft is as a promising but under-documented fixed-wing platform whose true value depends on what the manufacturer or dealer can verify directly.<\/p>\n\n\n\n
Overview<\/h2>\n\n\n\n
What kind of drone is it?<\/h3>\n\n\n\n
The Hacker HAES 90 is a fixed-wing UAV positioned in the commercial\/utility segment. Unlike quadcopters and other multirotors, a fixed-wing platform is typically designed to cover ground efficiently in forward flight. That usually makes it more attractive for mapping, route monitoring, agricultural observation, land management, and other missions where the aircraft needs to travel over larger areas instead of holding a stationary hover over a single point.<\/p>\n\n\n\n
That distinction is important. A multirotor is often chosen because it can take off vertically, stop in place, maneuver precisely in tight spaces, and inspect a structure from close range. A fixed-wing aircraft is usually chosen because it can fly farther or more efficiently over a broader area on the same energy budget. In other words, the HAES 90 belongs to a category where mission efficiency is often the main selling point.<\/p>\n\n\n\n
The \u201ccommercial\/utility\u201d label also suggests that this is not intended as a recreational aircraft or a camera drone for casual content creation. In drone-market terms, \u201cutility\u201d usually points toward practical work: surveys, monitoring, field data collection, site awareness, corridor observation, or sector-specific deployments where the aircraft is just one part of a larger operational workflow.<\/p>\n\n\n\n
Who should buy it?<\/h3>\n\n\n\n
The most likely audience is a professional operator, research team, integrator, or enterprise buyer comparing fixed-wing aircraft for field work. It may also interest analysts and journalists tracking lesser-known European drone platforms, especially those from the Czech Republic.<\/p>\n\n\n\n
More specifically, the HAES 90 could fit the early research phase for:<\/p>\n\n\n\n
\n
Survey and geospatial teams<\/strong> looking for fixed-wing efficiency<\/li>\n
Infrastructure and utility operators<\/strong> evaluating corridor coverage tools<\/li>\n
Environmental researchers<\/strong> who need repeatable outdoor flight over land areas<\/li>\n
Industrial operators<\/strong> wanting broader site awareness than a hovering drone can provide efficiently<\/li>\n
Procurement teams<\/strong> exploring alternatives to the most common Western enterprise UAV brands<\/li>\n
Training organizations or test programs<\/strong> comparing different UAV form factors<\/li>\n<\/ul>\n\n\n\n
However, it is probably not the right starting point for buyers who want a frictionless procurement process with abundant online documentation, transparent pricing, and a mature accessories ecosystem. Those buyers typically benefit from more widely documented platforms unless the HAES 90 offers a very specific advantage that only the manufacturer can demonstrate.<\/p>\n\n\n\n
What makes it different?<\/h3>\n\n\n\n
What stands out from the confirmed data is the combination of a 2.4 m wingspan, 1 hour endurance, and a 90 km\/h top speed in a utility-focused fixed-wing format. That places it in a more serious operational class than compact consumer drones and suggests that the design is meant for practical field deployment.<\/p>\n\n\n\n
At the same time, its distinction is currently limited by how little is publicly documented. There is no confirmed payload story, no confirmed autonomy stack, no confirmed software ecosystem, and no confirmed support structure in the supplied data. So what makes it different today is less about a clearly proven payload or workflow advantage and more about its positioning: it appears to be a classic fixed-wing utility aircraft from a Czech manufacturer, with enough core flight data to attract attention but not enough surrounding detail to remove procurement uncertainty.<\/p>\n\n\n\n
That means the HAES 90 may be most interesting for buyers comfortable doing direct vendor qualification. If you are willing to ask the manufacturer for manuals, payload compatibility documents, support terms, and regulatory details, it could be worth deeper investigation. If you need a fully self-service buying experience from public web material alone, it is harder to assess.<\/p>\n\n\n\n
Key Features<\/h2>\n\n\n\n
\n
Fixed-wing airframe<\/strong> for efficient forward flight over larger areas than many multirotors can cover per battery cycle. This is the defining feature of the aircraft and the reason it belongs in enterprise area-coverage discussions.<\/li>\n
Commercial\/utility positioning<\/strong> aimed at professional rather than casual consumer use. That suggests a mission-first design philosophy, even if the exact mission kit is not publicly detailed.<\/li>\n
1 hour endurance<\/strong> based on the supplied master record. For many field operators, this is a meaningful headline figure because it can support longer route flights and fewer battery changes than short-endurance systems.<\/li>\n
10 km range<\/strong> based on the supplied master record. This is a useful published number, though buyers should verify exactly what \u201crange\u201d means in the vendor\u2019s specification method.<\/li>\n
90 km\/h max speed<\/strong> based on the supplied master record. That implies a relatively purposeful airframe rather than a slow platform designed only for local loitering.<\/li>\n
300 m ceiling<\/strong> listed in the supplied data. As always, this should be treated as a platform capability figure, not a blanket legal flight permission.<\/li>\n
2.4 m wingspan<\/strong> indicating a larger field-deployed airframe rather than a compact foldable drone. This usually means better aerodynamic efficiency, but it also means more transport and setup planning.<\/li>\n
Czech origin<\/strong> for buyers comparing regional manufacturers and non-mainstream enterprise platforms. Country of origin can matter in procurement, service access, or supply-chain considerations.<\/li>\n
Payload, camera, autonomy, and software details not publicly confirmed<\/strong> in the supplied data. This is not a feature in the positive sense, but it is a critical reality of the current information picture and must shape how the aircraft is evaluated.<\/li>\n<\/ul>\n\n\n\n
Taken together, the confirmed features describe the HAES 90 as an airframe-led product. What we can see publicly is the basic flight envelope and physical class. What we cannot yet see is the broader operating ecosystem that often determines whether a commercial drone is merely interesting or genuinely practical.<\/p>\n\n\n\n
Full Specifications Table<\/h2>\n\n\n\n
\n\n
\n
Field<\/th>\n
Value<\/th>\n<\/tr>\n<\/thead>\n
\n
\n
Brand<\/td>\n
Hacker<\/td>\n<\/tr>\n
\n
Model<\/td>\n
HAES 90<\/td>\n<\/tr>\n
\n
Drone Type<\/td>\n
Fixed-wing<\/td>\n<\/tr>\n
\n
Country of Origin<\/td>\n
Czech Republic<\/td>\n<\/tr>\n
\n
Manufacturer<\/td>\n
Hacker<\/td>\n<\/tr>\n
\n
Year Introduced<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Status<\/td>\n
Unknown<\/td>\n<\/tr>\n
\n
Use Case<\/td>\n
Commercial\/utility<\/td>\n<\/tr>\n
\n
Weight<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Dimensions (folded\/unfolded)<\/td>\n
Wingspan 2.4 m; length and folded dimensions not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Max Takeoff Weight<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Battery Type<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Battery Capacity<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Flight Time<\/td>\n
1 hour<\/td>\n<\/tr>\n
\n
Charging Time<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Max Range<\/td>\n
10 km<\/td>\n<\/tr>\n
\n
Transmission System<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Top Speed<\/td>\n
90 km\/h<\/td>\n<\/tr>\n
\n
Wind Resistance<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Navigation System<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Obstacle Avoidance<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Camera Resolution<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Video Resolution<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Frame Rates<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Sensor Size<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Gimbal<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Zoom<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Storage<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Controller Type<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
App Support<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Autonomous Modes<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Payload Capacity<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Operating Temperature<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Water Resistance<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Noise Level<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Remote ID Support<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Geo-fencing<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Certifications<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
MSRP \/ Launch Price<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Current Price<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
\n
Operating Ceiling<\/td>\n
300 m<\/td>\n<\/tr>\n
\n
Wingspan<\/td>\n
2.4 m<\/td>\n<\/tr>\n
\n
Length<\/td>\n
Not publicly confirmed in supplied data<\/td>\n<\/tr>\n
A useful caution here: unknown fields should not automatically be read as missing features. They simply are not publicly confirmed in the supplied data. The HAES 90 may support some of these capabilities, but until documentation is available, buyers should treat them as open questions rather than assumed strengths.<\/p>\n\n\n\n
Design and Build Quality<\/h2>\n\n\n\n
The confirmed 2.4 m wingspan places the HAES 90 in a more serious field-deployed class than small foldable consumer drones. That usually suggests better aerodynamic efficiency and stronger suitability for outdoor mission work, but it also implies more transport and setup planning. A wingspan of this size generally points to an aircraft that will need deliberate handling, proper packing, and an operational area that suits fixed-wing flight rather than improvised launch from a cramped site.<\/p>\n\n\n\n
In practical terms, airframe size affects more than just performance. It can influence:<\/p>\n\n\n\n
\n
the size of the vehicle case or transport solution<\/li>\n
whether one person can deploy the system comfortably<\/li>\n
the amount of launch and recovery space needed<\/li>\n
how vulnerable the aircraft may be to rough handling in transit<\/li>\n
how easy it is to store spare wings or replacement parts<\/li>\n
how simple it is to assemble in the field under time pressure<\/li>\n<\/ul>\n\n\n\n
Because the supplied data does not confirm materials, fuselage construction, landing gear, or launch-and-recovery method, build quality can only be discussed in broad fixed-wing terms. A platform of this size is likely to matter more for operational readiness than for casual portability. Buyers should not think of the HAES 90 the way they would think of a compact folding camera drone that fits in a backpack and can be airborne in moments. Even if deployment is straightforward, the mission style is fundamentally different.<\/p>\n\n\n\n
battery access and swap time<\/strong><\/li>\n<\/ul>\n\n\n\n
Each of those questions affects real ownership value. For example, a modular wing attachment system can make transport easier and reduce downtime after minor damage. A clean battery access design can shorten turnaround between flights. A practical recovery method can determine whether the aircraft is suitable for rough terrain, grassy fields, agricultural strips, or industrial sites with limited clear landing areas.<\/p>\n\n\n\n
The missing design details also matter for maintenance. Fixed-wing UAVs can be excellent for efficient coverage, but they often place more importance on airframe integrity, control-surface alignment, propulsion tuning, and launch\/recovery wear than many casual users expect. A professional operator should want to know whether the aircraft uses common parts, whether the manufacturer provides service manuals, and whether critical components can be replaced at field level or only through a factory repair channel.<\/p>\n\n\n\n
If your workflow involves rugged deployment, the unknowns here are important. An enterprise drone is not just a flying object; it is a supportable system. For the HAES 90, the available public data gives a sense of scale and intended role, but not yet enough detail to judge how durable or service-friendly the airframe really is.<\/p>\n\n\n\n
Flight Performance<\/h2>\n\n\n\n
On paper, the HAES 90 shows a useful set of headline numbers for a utility fixed-wing platform: 1 hour endurance, 10 km range, and 90 km\/h top speed. Those figures suggest an aircraft intended for outdoor mission work rather than close-range hovering or cinematic flying. They also indicate a platform that should be evaluated in the context of route efficiency, area coverage, and mission planning rather than close-proximity inspection.<\/p>\n\n\n\n
A few practical takeaways:<\/p>\n\n\n\n
\n
Endurance:<\/strong> 1 hour is respectable for a utility UAV and can be meaningful for mapping, route observation, or broad-area site checks.<\/li>\n
Speed:<\/strong> 90 km\/h is fast enough to indicate a mission-oriented airframe rather than a slow loiter-only design.<\/li>\n
Range:<\/strong> 10 km is useful, though not exceptional by enterprise fixed-wing standards.<\/li>\n
Ceiling:<\/strong> The listed 300 m ceiling should be read as a platform figure, not a universal legal operating allowance.<\/li>\n<\/ul>\n\n\n\n
That said, headline numbers always need context.<\/p>\n\n\n\n
Endurance in real missions<\/h3>\n\n\n\n
A published endurance figure of 1 hour can be valuable, but in professional operations the real question is what that means under payload load, in wind, with operational reserve, and at a practical cruise speed rather than a best-case benchmark. A fixed-wing drone may technically remain airborne for a stated duration, but usable mission time can vary significantly depending on:<\/p>\n\n\n\n
\n
payload weight<\/li>\n
aerodynamic drag from sensor integration<\/li>\n
cruise speed selection<\/li>\n
route shape and number of turns<\/li>\n
wind conditions<\/li>\n
temperature and battery health<\/li>\n
reserve margin required by the operator<\/li>\n<\/ul>\n\n\n\n
So while 1 hour is a positive data point, buyers should ask whether it reflects an empty airframe, a specific payload class, or a standard mission configuration.<\/p>\n\n\n\n
Speed and what it actually means<\/h3>\n\n\n\n
The listed 90 km\/h top speed makes the HAES 90 sound relatively brisk, but maximum speed is not the same as efficient survey speed or best-endurance cruise. In fixed-wing operations, useful performance usually comes from the relationship between cruise efficiency, stability, and mission geometry. A high top speed may help with transit segments or wind penetration, but it does not automatically mean better mapping quality or easier sensor use.<\/p>\n\n\n\n
For example, some missions benefit from flying faster across open terrain, while others need slower, steadier passes to support overlap requirements or improve image capture consistency. Without a documented cruise-speed range, stall characteristics, or payload stabilization details, we cannot say exactly how the HAES 90 behaves in the mission envelope that matters most.<\/p>\n\n\n\n
Range and an important ambiguity<\/h3>\n\n\n\n
The stated 10 km range is helpful, but it is one of the specs that deserves direct clarification from the manufacturer. In drone listings, \u201crange\u201d can mean different things depending on how the source defines it. It may refer to command-and-control link range, telemetry distance, recommended operational radius, or another standardized measure. Sparse public documentation makes it hard to know exactly how that number was generated.<\/p>\n\n\n\n
This matters because a 10 km range figure does not automatically tell you how much area can be covered in a mapping mission, how far the aircraft can safely travel out and back with reserve, or whether the same number applies in all radio environments. Buyers should ask for the test basis behind the figure and whether regional regulations or radio configurations affect it.<\/p>\n\n\n\n
Ceiling and legal operations<\/h3>\n\n\n\n
The listed 300 m ceiling should not be interpreted as permission to fly at 300 m in normal operations. In most jurisdictions, legal altitude limits are determined by aviation regulations, mission approvals, and airspace restrictions, not by the aircraft\u2019s technical capability. The ceiling number is best treated as part of the performance envelope, not an operational default.<\/p>\n\n\n\n
Fixed-wing mission character<\/h3>\n\n\n\n
Because the propulsion system, cruise speed, wind performance, and control link are not confirmed, the exact flight character remains unclear. As analysis rather than confirmed fact, a fixed-wing aircraft with a 2.4 m span will typically favor efficient outdoor routes and smoother forward flight over the stationary precision that multirotors offer.<\/p>\n\n\n\n
That means the HAES 90 is likely best viewed as:<\/p>\n\n\n\n
\n
an outdoor coverage tool<\/strong><\/li>\n
a route-oriented aircraft<\/strong><\/li>\n
a better fit for open spaces than tight infrastructure<\/strong><\/li>\n
a poor match for indoor use<\/strong><\/li>\n
a specialized option for operators comfortable with fixed-wing planning<\/strong><\/li>\n<\/ul>\n\n\n\n
Indoor use is not realistic. This is an outdoor mission aircraft.<\/p>\n\n\n\n
The broader conclusion is simple: the published flight figures are credible enough to make the HAES 90 worth investigating, but not detailed enough to tell the full performance story. Professional buyers should request mission-specific performance data, especially if they plan to use the aircraft in wind, at higher elevations, with payloads, or under strict operational safety procedures.<\/p>\n\n\n\n
Camera \/ Payload Performance<\/h2>\n\n\n\n
This is the biggest information gap in the public record.<\/p>\n\n\n\n
No camera, gimbal, payload capacity, sensor type, or payload interface is confirmed in the supplied data. That means the HAES 90 cannot currently be recommended as a photography drone, mapping drone, thermal drone, or inspection drone on payload merit alone.<\/p>\n\n\n\n
This is not a small omission. In commercial UAV procurement, the payload often matters more than the airframe. Many aircraft can stay in the air for an hour. Far fewer can do so while carrying the right sensor, with stable data capture, reliable geotagging, manageable post-processing, and a workflow that fits the mission objective.<\/p>\n\n\n\n
What that means for buyers:<\/p>\n\n\n\n
\n
If you need survey accuracy<\/strong>, verify compatible mapping cameras and georeferencing workflow.<\/li>\n
If you need inspection value<\/strong>, verify zoom, stabilization, and slow-flight behavior.<\/li>\n
If you need monitoring or public-safety utility<\/strong>, verify sensor power, transmission, and integration.<\/li>\n
If you need content creation<\/strong>, this model is not documented well enough to assess.<\/li>\n<\/ul>\n\n\n\n
A serious buyer should also verify several payload questions that are often overlooked:<\/p>\n\n\n\n
\n
Is there a standard payload bay<\/strong> or a custom integration requirement?<\/li>\n
What is the maximum payload mass<\/strong> and how does it affect endurance?<\/li>\n
Does the aircraft supply power output<\/strong> for onboard sensors?<\/li>\n
Is there a payload trigger interface<\/strong> for mapping cameras?<\/li>\n
Are there options for thermal, multispectral, or RGB mapping sensors<\/strong>?<\/li>\n
Does the system support real-time video downlink<\/strong>, data logging only, or both?<\/li>\n
How is the payload mounted and balanced with respect to the aircraft\u2019s center of gravity?<\/li>\n
Is there any support for PPK\/RTK workflows<\/strong>, external GNSS logging, or survey-grade metadata?<\/li>\n
Can payloads be swapped in the field without reconfiguration complexity?<\/li>\n<\/ul>\n\n\n\n
Without answers to those questions, the HAES 90 remains an airframe candidate rather than a completed mission solution.<\/p>\n\n\n\n
That does not mean it lacks capability. It may well support useful sensors. But enterprise operators should resist the temptation to assume that any fixed-wing drone with decent endurance is automatically a mapping platform. Survey work, thermal work, and inspection work each impose different requirements on camera quality, integration, stabilization, image timing, and software support.<\/p>\n\n\n\n
In short, the airframe may be suitable for utility work, but the payload story is not publicly confirmed. Until that changes, the HAES 90 should be evaluated as a potentially capable platform whose mission value depends almost entirely on the sensor package and integration details the vendor can provide.<\/p>\n\n\n\n
Smart Features and Software<\/h2>\n\n\n\n
No software ecosystem details are confirmed in the supplied data. That includes common professional-buying questions such as:<\/p>\n\n\n\n
\n
return-to-home or return-to-launch behavior<\/li>\n
waypoint mission planning<\/li>\n
autonomous mapping modes<\/li>\n
SDK or API support<\/li>\n
cloud fleet tools<\/li>\n
mobile app support<\/li>\n
data export workflows<\/li>\n
geofencing<\/li>\n
Remote ID support<\/li>\n<\/ul>\n\n\n\n
For a commercial\/utility drone, those missing details matter almost as much as the airframe itself. In many enterprise deployments, software determines whether the aircraft is practical at scale. A drone can have good endurance and still be a poor procurement choice if the mission planning tools are limited, the logs are hard to access, the firmware process is opaque, or the workflow cannot integrate into an existing geospatial or inspection stack.<\/p>\n\n\n\n
Buyers should request official documentation covering:<\/p>\n\n\n\n
\n
autopilot functions<\/li>\n
mission planning tools<\/li>\n
firmware support cadence<\/li>\n
logging and telemetry exports<\/li>\n
failsafe behavior<\/li>\n
lost-link procedures<\/li>\n
operator permission levels<\/li>\n
maintenance alerts or system health reporting<\/li>\n
integration with mapping or inspection workflows<\/li>\n<\/ul>\n\n\n\n
A few software-specific questions are especially important for fixed-wing systems. Does the aircraft support automated survey grids? Does it offer terrain-following capability if the route crosses uneven ground? Can the operator define recovery behavior clearly? Is there simulation or training mode support? Are there audit logs for enterprise reporting? These are the kinds of questions that often separate a usable commercial system from a merely capable flying platform.<\/p>\n\n\n\n
If you manage more than one aircraft, software maturity becomes even more important. Fleet administrators may need role-based access, mission archiving, exportable flight logs, maintenance tracking, and repeatable route planning. None of that is publicly confirmed for the HAES 90 from the supplied data.<\/p>\n\n\n\n
So the right conclusion is not that the HAES 90 lacks smart features, but that they are currently undocumented in a way that prevents a confident assessment. For enterprise buyers, this should trigger a documentation request, not an assumption.<\/p>\n\n\n\n
Use Cases<\/h2>\n\n\n\n
Based on its confirmed airframe type and published flight figures, the HAES 90 appears most realistic for the following roles, depending on payload configuration:<\/p>\n\n\n\n
\n
\n
local-area mapping and survey work<\/strong>\n A fixed-wing design can be efficient for planned coverage missions over land parcels, fields, or open sites. Whether the HAES 90 is truly suitable depends on the availability of mapping payloads, triggering support, and georeferenced workflow compatibility.<\/p>\n<\/li>\n
\n
utility and infrastructure corridor observation<\/strong>\n Pipelines, roads, power routes, and similar corridors often benefit from forward-flight efficiency. A platform with respectable endurance and speed could make sense here, especially where long straight segments matter more than hover inspection.<\/p>\n<\/li>\n
\n
environmental and land monitoring<\/strong>\n Conservation groups, land managers, and research teams often need repeated flights over outdoor areas. A fixed-wing airframe can be attractive for this kind of monitoring, assuming sensor compatibility and repeatable mission planning are available.<\/p>\n<\/li>\n
\n
industrial site coverage over larger outdoor spaces<\/strong>\n Mines, energy sites, logistics zones, and large facilities may need broad situational coverage rather than close-up static inspection. A fixed-wing aircraft can support that mission profile if the launch\/recovery site is suitable.<\/p>\n<\/li>\n
\n
fixed-wing operator training and evaluation<\/strong>\n Organizations comparing operational concepts may find the HAES 90 useful as a platform for testing fixed-wing workflows, crew requirements, and deployment methods relative to multirotor fleets.<\/p>\n<\/li>\n
\n
research or program-level assessment of field UAV platforms<\/strong>\n Academic labs, public-sector pilot programs, and technical evaluators sometimes assess lesser-known regional UAV systems. The HAES 90 could be relevant in that context, particularly if direct manufacturer engagement is possible.<\/p>\n<\/li>\n<\/ul>\n\n\n\n
Payload-specific missions should only be assumed after sensor compatibility is confirmed.<\/p>\n\n\n\n
It is equally important to identify what the HAES 90 is probably not<\/strong> best at. It does not appear, based on the available data, to be the obvious choice for close-range facade inspection, indoor documentation, cinematic hovering shots, or any mission where vertical takeoff, precision station-keeping, and obstacle-rich maneuvering are the main requirements. Even if it offers some autonomous capability, the basic fixed-wing form still points toward open-air route work.<\/p>\n\n\n\n
The key takeaway is that the HAES 90 seems best aligned with coverage-oriented missions<\/strong>, not hover-centric missions<\/strong>. That is its likely operational niche.<\/p>\n\n\n\n
Pros and Cons<\/h2>\n\n\n\n
Pros<\/h3>\n\n\n\n
\n
Fixed-wing efficiency<\/strong> is typically better than multirotors for covering larger outdoor areas, which makes the HAES 90 relevant for route and land-coverage workflows.<\/li>\n
1 hour flight time<\/strong> is a useful headline figure for field operations and may reduce battery swaps compared with shorter-endurance systems.<\/li>\n
90 km\/h top speed<\/strong> suggests a mission-capable utility airframe rather than a casual or entry-level design.<\/li>\n
2.4 m wingspan<\/strong> points to a serious outdoor platform rather than a toy or ultra-compact consumer aircraft.<\/li>\n
Commercial\/utility positioning<\/strong> may suit enterprise workflows better than consumer-oriented drones if the software and payload ecosystem are also mature.<\/li>\n
Czech origin<\/strong> may interest buyers comparing regional industrial drone suppliers or seeking non-mainstream procurement options.<\/li>\n<\/ul>\n\n\n\n
Cons<\/h3>\n\n\n\n
\n
Payload details are not publicly confirmed<\/strong>, which is a major issue for enterprise buyers because the sensor package often defines mission value.<\/li>\n
Price is not publicly confirmed<\/strong>, making budgeting and total-cost comparison difficult.<\/li>\n
Current status is unknown<\/strong>, which raises procurement, warranty, and long-term support questions.<\/li>\n
Software and autonomy features are not publicly confirmed<\/strong>, limiting confidence in mission planning and operational integration.<\/li>\n
Weight and MTOW are not publicly confirmed<\/strong>, complicating regulatory planning and category assessment.<\/li>\n
Range of 10 km may be modest<\/strong> compared with some other enterprise fixed-wing platforms, depending on how the figure is defined.<\/li>\n
Support network and spare-parts situation are not publicly confirmed<\/strong>, which is a real risk for field operations.<\/li>\n
No confirmed camera specs<\/strong> means it is hard to judge mission value beyond the airframe itself.<\/li>\n<\/ul>\n\n\n\n
In short, the pros are real but mostly airframe-level. The cons are mostly ecosystem-level. For professional buyers, ecosystem gaps can outweigh good headline flight numbers very quickly.<\/p>\n\n\n\n
Comparison With Other Models<\/h2>\n\n\n\n
Because public HAES 90 data is limited, the comparisons below are directional market references rather than perfect one-to-one spec matches.<\/p>\n\n\n\n
\n\n
\n
Model<\/th>\n
Price<\/th>\n
Flight Time<\/th>\n
Camera or Payload<\/th>\n
Range<\/th>\n
Weight<\/th>\n
Best For<\/th>\n
Winner<\/th>\n<\/tr>\n<\/thead>\n
\n
\n
Hacker HAES 90<\/td>\n
Not publicly confirmed in supplied data<\/td>\n
1 hour<\/td>\n
Not publicly confirmed in supplied data<\/td>\n
10 km<\/td>\n
Not publicly confirmed in supplied data<\/td>\n
Fixed-wing commercial\/utility missions with faster forward-flight emphasis<\/td>\n
Baseline<\/td>\n<\/tr>\n
\n
senseFly eBee X<\/td>\n
Enterprise quote, varies by package<\/td>\n
Up to 90 min<\/td>\n
Mature mapping payload ecosystem<\/td>\n
Varies by configuration and region<\/td>\n
Verify by configuration<\/td>\n
Established mapping and survey workflows<\/td>\n
eBee X for documented ecosystem maturity<\/td>\n<\/tr>\n
\n
WingtraOne GEN II<\/td>\n
Enterprise quote, varies by package<\/td>\n
Up to 59 min<\/td>\n
Survey and mapping payload ecosystem<\/td>\n
Varies by configuration and region<\/td>\n
Verify by configuration<\/td>\n
VTOL mapping where vertical takeoff and landing matter<\/td>\n
WingtraOne for tight launch sites<\/td>\n<\/tr>\n
\n
senseFly eBee Plus<\/td>\n
Legacy pricing varies by used market and package<\/td>\n
Depends on support and documentation access<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n
The most important thing to understand in this section is that these comparisons are not meant to prove that the HAES 90 is better or worse in absolute terms. They are meant to show the kind of market context a buyer should use. The big differentiator here is not just performance; it is documentation, ecosystem maturity, and integration confidence.<\/p>\n\n\n\n
HAES 90 vs a close competitor<\/h3>\n\n\n\n
Against the senseFly eBee X, the HAES 90 has a respectable published top speed and a solid 1-hour endurance figure. The difference is transparency: eBee X is easier to evaluate because its mapping ecosystem and market presence are better documented. If your priority is procurement certainty, the eBee X is the safer comparison point.<\/p>\n\n\n\n
That matters in practice. A documented payload matrix, training resources, and established user base can reduce deployment risk dramatically. The HAES 90 might still be a valid alternative if it offers a pricing, support, or customization advantage through direct vendor engagement, but that advantage is not visible from the supplied data alone.<\/p>\n\n\n\n
HAES 90 vs an alternative in the same segment<\/h3>\n\n\n\n
The WingtraOne GEN II is not a traditional fixed-wing-only aircraft, so the real comparison is workflow philosophy. The HAES 90 may appeal more to buyers who specifically want a classic fixed-wing airframe, while WingtraOne is stronger where vertical takeoff and landing reduce field constraints.<\/p>\n\n\n\n
This is often a more important distinction than raw endurance. If your launch environment is constrained, VTOL can simplify operations substantially. If you already have open launch and recovery space and want a conventional fixed-wing profile, the HAES 90 may be more conceptually aligned. But again, payload and software documentation would need to confirm whether that alignment translates into practical mission value.<\/p>\n\n\n\n
HAES 90 vs an older or previous-generation option<\/h3>\n\n\n\n
Compared with older fixed-wing survey platforms like the senseFly eBee Plus, the HAES 90 looks viable on headline speed and endurance. The tradeoff is uncertainty: older legacy models can sometimes have clearer documentation and a more established used-market knowledge base than lesser-documented current or unknown-status platforms.<\/p>\n\n\n\n
That creates an unusual situation. A lesser-known aircraft is not automatically worse than a legacy model, but if documentation is thin, buyers may find that an older, well-understood system is actually easier to support operationally. This is especially true for institutions that value predictability over experimentation.<\/p>\n\n\n\n
Overall, the HAES 90\u2019s competitive position is best described as potentially credible, but insufficiently transparent<\/strong>. It belongs in comparisons, but not at the top of a shortlist unless the manufacturer can fill in the missing details convincingly.<\/p>\n\n\n\n
Manufacturer Details<\/h2>\n\n\n\n
The supplied record identifies Hacker<\/strong> as both the brand<\/strong> and the manufacturer<\/strong>, with Czech Republic<\/strong> listed as the country of origin. That means there is no separate brand-versus-manufacturer distinction confirmed in the available data for this model.<\/p>\n\n\n\n
European origin may matter to some buyers for procurement, servicing, logistics, standards alignment, or strategic sourcing reasons. For others, it may simply be a point of market interest. Either way, country of origin alone does not tell you enough about the current company profile, support reach, or product maturity.<\/p>\n\n\n\n
What is not publicly confirmed in the supplied record:<\/p>\n\n\n\n
\n
company founding year<\/li>\n
headquarters city<\/li>\n
parent company context<\/li>\n
broader drone portfolio<\/li>\n
official market reputation beyond this model listing<\/li>\n<\/ul>\n\n\n\n
So, while the HAES 90 is clearly associated with a Czech manufacturer named Hacker, buyers should verify the company\u2019s current corporate profile and active drone business status before making procurement decisions.<\/p>\n\n\n\n
A few practical due-diligence steps are worth mentioning here:<\/p>\n\n\n\n
\n
confirm whether the drone business is active and ongoing<\/strong><\/li>\n
verify whether the HAES 90 is a current product, legacy model, or special-order platform<\/strong><\/li>\n
ask for official brochures, manuals, and warranty terms<\/strong><\/li>\n
confirm regional sales contacts<\/strong><\/li>\n
request references or example deployments if available<\/li>\n<\/ul>\n\n\n\n
This is especially important when evaluating lesser-documented enterprise systems. A strong manufacturer relationship can offset limited public information, but only if responsiveness, support terms, and technical clarity are all good.<\/p>\n\n\n\n
Support and Service Providers<\/h2>\n\n\n\n
Support details are not publicly confirmed in the supplied data, and that is significant for a utility fixed-wing drone. Before purchase, buyers should verify:<\/p>\n\n\n\n
\n
official technical support channels<\/li>\n
repair turnaround options<\/li>\n
spare parts stock<\/li>\n
battery replacement availability<\/li>\n
airframe consumables and crash repair support<\/li>\n
firmware update process<\/li>\n
training or onboarding options<\/li>\n
regional dealer or service partner coverage<\/li>\n<\/ul>\n\n\n\n
For enterprise UAVs, support quality can matter more than raw specs. An aircraft with attractive endurance numbers can still become a poor investment if repairs are slow, replacement wings are hard to source, or only a single service point exists for a wide region. Fixed-wing systems can also involve repair items that are easy to underestimate, such as control surfaces, wing joints, nose sections, propulsive components, and landing-related wear.<\/p>\n\n\n\n
Buyers should also ask support questions in operational terms:<\/p>\n\n\n\n
\n
What is the expected turnaround for a damaged airframe?<\/li>\n
Can routine maintenance be handled locally?<\/li>\n
Are training materials available for crew onboarding?<\/li>\n
Is there a defined spare-parts package for field teams?<\/li>\n
How are firmware and safety notices communicated?<\/li>\n
Is there any service-level commitment for business customers?<\/li>\n<\/ul>\n\n\n\n
If the HAES 90 is still active in the market, readers should confirm official support and regional service availability directly through the brand or an authorized reseller. This is one of the main areas where direct contact will tell you far more than public listings can.<\/p>\n\n\n\n
Where to Buy<\/h2>\n\n\n\n
There is no publicly confirmed retail channel in the supplied data.<\/p>\n\n\n\n
Given its commercial\/utility positioning, the HAES 90 is more likely to be sourced through:<\/p>\n\n\n\n
It does not appear, from the supplied data alone, to be a mainstream consumer retail drone. Buyers should expect quote-based purchasing rather than simple off-the-shelf checkout unless a verified dealer listing says otherwise.<\/p>\n\n\n\n
That usually means the buying process may involve a request for information, a mission consultation, optional payload configuration, lead-time confirmation, and a formal quote rather than instant online ordering. For commercial operators, that is normal. But it does make vendor responsiveness an important part of the evaluation. If basic pre-sales questions are hard to answer, that is often a useful signal in itself.<\/p>\n\n\n\n
Price and Cost Breakdown<\/h2>\n\n\n\n
Launch price and current market price are not publicly confirmed in the supplied data.<\/p>\n\n\n\n
For budgeting, prospective buyers should verify more than just the airframe price. A realistic commercial UAV cost picture may include:<\/p>\n\n\n\n
\n
base aircraft<\/li>\n
batteries<\/li>\n
charger and power accessories<\/li>\n
ground control equipment<\/li>\n
payload or sensor package<\/li>\n
mission planning or data processing software<\/li>\n
transport case<\/li>\n
spare propellers or propulsion components<\/li>\n
airframe spare parts<\/li>\n
operator training<\/li>\n
maintenance and repair costs<\/li>\n
insurance<\/li>\n
regulatory compliance costs<\/li>\n<\/ul>\n\n\n\n
With a fixed-wing commercial platform, these add-ons can materially change the real ownership cost. If you are comparing the HAES 90 with more documented alternatives, total workflow cost may matter more than the sticker price.<\/p>\n\n\n\n
A few hidden or semi-hidden cost categories are especially worth checking:<\/p>\n\n\n\n
\n
software subscriptions<\/strong> for mission planning or cloud management<\/li>\n
survey processing software<\/strong> if the intended use is mapping<\/li>\n
import, shipping, or customs costs<\/strong><\/li>\n
extra batteries for back-to-back field days<\/strong><\/li>\n
training time for fixed-wing-specific operation<\/strong><\/li>\n
consumable parts for launch and recovery wear<\/strong><\/li>\n
warranty extensions or support contracts<\/strong><\/li>\n<\/ul>\n\n\n\n
For some organizations, the cheapest airframe is not the lowest-cost option over two years. If a more documented aircraft comes with easier software, faster repair access, and better training materials, its total operational cost may actually be lower. The HAES 90 could still be competitive, but the missing public price information means buyers need a full quote package before making meaningful comparisons.<\/p>\n\n\n\n
Regulations and Compliance<\/h2>\n\n\n\n
As a practical rule, buyers should treat the HAES 90 like any other commercial UAV platform and verify compliance locally before flying.<\/p>\n\n\n\n
Key points to check:<\/p>\n\n\n\n
\n
operator registration requirements<\/li>\n
pilot competency or licensing requirements<\/li>\n
airspace restrictions<\/li>\n
altitude limits<\/li>\n
visual line of sight versus BVLOS rules<\/li>\n
privacy and data-protection obligations<\/li>\n
site-specific permissions for industrial or utility work<\/li>\n
whether Remote ID is required in your jurisdiction<\/li>\n
whether the aircraft\u2019s weight class changes the approval path<\/li>\n<\/ul>\n\n\n\n
Because the HAES 90\u2019s weight, class marking, and Remote ID status are not publicly confirmed, operators should not assume it fits neatly into any consumer-friendly category. Also, the published 300 m ceiling does not override legal altitude limits, which are often lower depending on country and mission type.<\/p>\n\n\n\n
This section matters even more for fixed-wing aircraft than for many consumer drones. A larger wingspan, different recovery profile, and potentially higher operating speed can affect risk assessment, operational procedures, and site suitability. In some jurisdictions, those factors may influence whether the aircraft is straightforward to operate under standard rules or better suited to more structured enterprise approvals.<\/p>\n\n\n\n
For example:<\/p>\n\n\n\n
\n
In European<\/strong> contexts, operators may need to consider class marking, category fit, and whether the mission belongs in open, specific, or another regulated framework.<\/li>\n
In the United States<\/strong>, operators may need to consider Part 107 limits, waivers, and whether the mission remains within standard visual line-of-sight rules.<\/li>\n
In industrial environments<\/strong>, site owner permissions and safety procedures may matter as much as national drone law.<\/li>\n
For survey or monitoring missions<\/strong>, data protection and privacy obligations may also apply.<\/li>\n<\/ul>\n\n\n\n
Since key technical classification details are not confirmed publicly, compliance planning for the HAES 90 should begin with the manufacturer\u2019s documentation, not assumptions based on general drone categories.<\/p>\n\n\n\n