InDro obtains FAA BVLOS waiver for solar farm inspections

InDro obtains FAA BVLOS waiver for solar farm inspections

By Scott Simmie

 

InDro Robotics has obtained what we believe to be a Canadian first: A waiver from the Federal Aviation Administration to conduct Beyond Visual Line of Sight flights.

The waiver will allow InDro to expand its successful program of remotely piloted infrastructure inspections where we ship a drone to the location – and instruct a person there to be a Visual Observer during the flight.

Specifically, the FAA waiver permits InDro to remotely operate drone inspections of fenced solar farms in Class G airspace, 10 miles (16 km) from airports. Operations can reach a maximum altitude of 400′ AGL.

The waiver opens the skies for InDro to tap into a large market, remotely inspecting some of the 2,500+ solar farms in the United States.

Below: A solar farm in Hawaii. Photo courtesty Reegan Moen, US Dept of Energy.

Solar Farm Inspection

Inspection without the hassle

 

Solar farms require regular inspection. Traditionally, these have been done by employees walking the grounds with a handheld thermal sensor, plus their own visual inspection. But this task is time-consuming, and can last days at a large facility.

As a result, many solar farms have switched – or are in the process of switching – to aerial inspection using drones. Combining visual and thermal inspection from above, issues with broken, malfunctioning and even dirty panels can be quickly identified. Many solar farms can be inspected in less than an hour and even large installations usually take less than a day.

But doing drone inspections with employees comes with a cost. The pilot must meet FAA Part 107 or Transport Canada standards. That involves training, time and money before even purchasing a drone. Plus, with next-generation drones coming out with better sensors, longer flight times and newer features, it doesn’t take long before that drone will require replacing.

The InDro Robotics solution is simple and cost-effective. We ship the client a current drone, suited to the task. We work with someone on-site, instructing them how to turn on the drone and act as a Visual Observer. One of our pilots then flies the mission remotely, maintaining continuous communication via phone with the visual observer.

With a solid 5G connection, data is uploaded directly to the cloud during the mission and processing begins. We can have a report identifying anomalies in the hands of most clients shortly after the mission. Once the flight is complete, the drone is packed up and shipped back to InDro.

We’ve done this at multiple facilities in Canada already, operating from hundreds of kilometres away. Receiving the FAA approval means we’ll be able to deploy the same solution in the United States.

And what does that look like? Well, like this – whether you’re 100 kilometres away or 5,000:

Rigorous criteria

 

As with Transport Canada’s Special Flight Operations Certificate (SFOC), obtaining an FAA waiver requires that an applicant satisfy the regulator on multiple fronts.

The FAA application, for those interested, asks a high number of detailed questions  requiring equally detailed answers. Here’s the first from the InDro application:

§ 107.31 Visual Line of Sight Aircraft Operation Question: Describe how the Remote Pilot in Command (RPIC) will be able to continuously know and determine the position, altitude, attitude, and movement of their small unmanned aircraft (sUA) or Drone and ensure the sUA or Drone remains in the area of intended operation without exceeding the performance capabilities of the command and control link. 

“When the RPIC or person operating the small unmanned aircraft system (sUAS) or Drone cannot see the sUA or Drone, how will they know, at all times, the current real-time: Geographic location Altitude above the ground Attitude (orientation, deck angle, pitch, bank), the direction of flight of the sUA or Drone…”

And that’s just one from a series of Q&As that stretched over seven dense pages of single-space text.

At the end of the day, however, it isn’t about individual answers. It’s more about the big picture of them taken collectively. Such permissions ultimately come down to this: The regulator must feel the mission poses minimal risk to crewed aircraft and people and property on the ground. They must also feel confident the operator has the expertise to carry out the mission as planned.

InDro satisfied this on both fronts, receiving a waiver valid until December 31, 2026.

We contacted the FAA Press Office to inquire whether any other Canadian company has ever received a waiver. They couldn’t answer that, stating that “Part 107 does not address company ownership, but restricts all 107 operations to ‘…within/in the United States.'”

 

FAA

A busy year of flying

 

We were in the air for clients – and for R&D – a lot in 2022. In fact, we recently tallied up our flights for an internal Town Hall meeting, and decided to share.

The high points?

  • A total of 336 flights carried out, including missions in Canada, the US, South America and Saudi Arabia
  • 40,802 aerial photos captured
  • 487 kilometres of flight using multirotor drones

“All of our field operations were successfully completed,” Flight Operations Lead and GIS specialist Eric Saczuk told staff during the Town Hall. “And that speaks a lot to the quality of the team – to all of the work that goes on in the background has allowed us to have that success rate.” 

During the townhall, it was revealed that the only incident encountered in 2022 operations was a landing gear issue on a single flight.

“If that’s all that happened with more than 400 active flights from all over the world,” he continued, “We’re doing something right. We have a great team, and great products.”

Below: A graphic from the internal InDro Town Hall showing highlights of the company’s drone operations:

FAA

InDro’s take

 

InDro began as an R&D company doing work exclusively in the drone space. And while we’ve expanded to ground robotics, pushing the envelope in the RPAS arena is still a very large chunk of what we do. Our new InDro Pilot software and hardware solution, for example, turns any Pixhawk-based Enterprise drone into a tele-operated system capable of dense and highly secure real-time uploads during missions.

The company has flown many Visual Line of Sight missions in the US already; the new FAA waiver will now allow InDro to deploy its teleoperated system.

“We’re pleased the FAA has seen fit to grant us this BVLOS waiver,” says InDro CEO Philip Reece. “Permitting these kinds of teleoperated missions will save clients both time and money, while ensuring they still receive best-in-class piloting and data acquisition/interpretation. We have deep expertise in solar farm inspections – and look forward to carrying out missions with this waiver.”

Interested in learning more? Feel free to contact Account Executive Luke Corbeth.

InDro hires Head of Strategic Innovations

InDro hires Head of Strategic Innovations

By Scott Simmie

 

As a Research and Development company, InDro Robotics is – by necessity – engineering-heavy. Our staff at Area X.O in Ottawa and in British Columbia are constantly pushing the envelope when it comes to inventing and deploying new solutions in hardware, software and service provision.

As a result, much of the focus of our hiring in the past couple of years has been expanding our engineering staff.

But with a growing number of InDro products and clients, it’s also important to identify and develop key partnerships. And on that front, we’re pleased to announce a non-engineer hire. Stacey Connors joins the InDro team as Head of Strategic Innovations.

The role is about the big picture – and a long-term vision of planning and executing InDro’s growth trajectory.

“My role is to find where we want to go, find the vertical that InDro should lean into, then determine what infrastructure we need based on our initial customer understanding and discoveries.”

It’s a big job. And Stacey comes with the requisite experience.

Stacey Connors

FedEx

Connors comes to InDro after a 12-year, high-level run at FedEx, the global leader in express transportation. Beginning as an account executive, she went on to positions in Strategic Development, became a Worldwide Account Manager, and was a District Manager when she made the leap to InDro.

Much of her work with FedEx involved B2B development. She worked with a variety of different verticals, including aerospace, retail, healthcare and manufacturing. She comes with a special knack for putting pieces together.

“What I enjoyed about it was twofold,” she says: “Finding the intersection between the solution that my organization had available and the need or problem that the customer’s trying to solve.”

Leap of faith

 

Connors says she truly enjoyed her work at FedEx. But when the opportunity at InDro came along, she felt ready for a new challenge that would push her beyond her comfort zone.

“I was craving something wildly different,” she says. “I hadn’t remotely thought about robotics and laughed when Peter (Peter King, Head of Robotic Solutions) first mentioned it. But it was a personal opportunity to get uncomfortable, be challenged, and work on the edge – where you have to be sharp.” 

Connors has quickly jumped in, traveling to Area X.O on her first week to meet a visiting robotics company from Europe and a delegation from NAV CANADA. While there, she quickly observed one of InDro’s key strengths.

“In my first few days it was very obvious that there’s a cohesiveness among all individuals in the organization. Everyone fully understands the business objectives we’re trying to achieve and the value that each of them bring,” she says. “When I walk into an organization and see that collective spirit, that’s the horse I’m going to bet on.”

 

Solutions

 

 

Drawing on her FedEx experience, Connors says she’s excited to start identifying companies that might benefit from InDro’s many robotic solutions – including a new inventory drone system that autonomously scans warehouse stock. But while sales may well result from her work, her role is really about the bigger strategic picture as InDro continues to grow.

“Yes, I’ll be leveraging our R&D capabilities to accelerate specific industries in their use of these technologies,” she says. “But I really see InDro as an integrator – and that’s almost how I would describe my role. We have research and development, the newest and latest and greatest. I’ll be going out and seeing who has other pieces we don’t have and bringing them all together. And that really gets me excited.”

Canada Robotics

Other expertise

 

Connors, in addition to her accomplishments at FedEx, has other expertise that will serve her well in this role. She has a Bachelor of Health Science from Wilfrid Laurier University,  along with a post-graduate degree from the University of the Sunshine Coast in Australia. She’s also a certified Talent Management Practitioner, has gone through the Ivey Sales Leadership Program, has studied Emotional Intelligence at McMaster’s DeGroote School of Business, and is also a Certified Multipliers Leader – with the latter meaning she has expertise to help bring out the greatness in others.

But she’d rather talk about InDro – and what she’s learned since coming onboard – than about herself.

“At FedEx our operators were the core and value of the company. And it is obvious that the engineers are the core value of this company,” she says. “Research and development is that incessant hunger to continue to provide new options, new solutions, new technologies. And you can feel that spirit here.”

Autonomous Cars

InDro’s take

 

The hiring of Stacey Connors as Head of Strategic Innovations is significant for a couple of reasons. The first, obviously, is that she brings proven skills, expertise, and an outstanding reputation.

But the second is really about the timing.

InDro Robotics has been growing steadily. In the last two years our team has developed and deployed multiple new products and services, and we are working with several global technology companies. Our engineering team has continued to grow.

“We are at a significant juncture in the company’s trajectory,” says CEO Philip Reece. “While InDro will always be an engineering-first firm, we are now at the stage of securing strategic partnerships to ensure the next phase of growth. Stacey is the right person, in the right position, at the right time.”

Police drone collision raises questions

Police drone collision raises questions

By Scott Simmie

 

There’s no question that drones have become an essential tool for First Responders.

They’re used to assess fires, document accidents, search for missing people and even get a sense of damage following a natural disaster like a tornado.

They’re also used by police on occasion to actively search for a suspect trying to evade capture. In such scenarios, you can imagine that officers might be highly focussed on apprehending the suspect.

That may have been a factor in an incident that occurred August 10, 2021. It involved a York Regional Police officer with an Advanced RPAS certificate, a DJI M210…and a Cessna. The incident is outlined in detail in a new Transportation Safety Board report.

(If you’ve read the report and just want to hear our take, skip to the end.)

Police Drone Collision

What happened

 

On August 10, 2021, a student pilot and flight instructor were in a Cessna 172N on a typical training flight. They were on final approach to Runway 15 at Toronto/Buttonville municipal airport. And then, in the words of the TSB report, this happened:

At approximately 1301 Eastern Daylight Time, the student pilot and flight instructor heard and felt a solid impact at the front of the aircraft. Suspecting a bird strike, they continued the approach and made an uneventful landing, exiting the runway and proceeding to park on the ramp. After parking the aircraft, they observed damage on the front left cowl under the propeller; however, there were no signs that a bird had struck the aircraft.

So what did?

Shortly afterward, a member of the York Regional Police reported to airport staff that he believed a collision had occurred between the remotely piloted aircraft he had been operating and another aircraft. The remotely piloted aircraft, a DJI Matrice M210 (registration C-2105569275), had been in a stationary hover at 400 feet above ground level when the 2 aircraft collided. The DJI Matrice M210 was destroyed.

There were no injuries to either pilot on the Cessna 172N or to persons on the ground.

Here’s a look at the runway, along with the location of the RPAS. (Looks like the report missed a “t” on the word “flight.”)

 

 

Police Drone Collision

The drone

 

York Regional Police (YRP) were looking for a potentially armed suspect, and called the YRP’s Air Support Unit (ASU) to assist at 12:02 pm. The pilot of the drone arrived at the scene at 12:20. The first flight of the DJI Matrice M210 took off at 12:32. Shortly after takeoff, the pilot asked some officers standing nearby to watch the drone during flight; one of the officers said they’d do the task.

After some initial reconaissance, the officer landed the flight 16 minutes later to change batteries. It was now 12:48.

“During this time,” says the report, “the pilots in the Cessna had completed their exercises in the practice area and were returning to the airport. They made the appropriate radio calls declaring their intention to fly over the airport and join the right-hand downwind for Runway 15. There was no other traffic broadcasting on the CYKZ mandatory frequency (MF) at the time, nor had the pilots heard any other transmissions on the frequency during their return flight.”

It’s worth noting the “Mandatory Frequency” here. This airport does not have a tower and its own Air Traffic Control. Aircraft are to announce their intentions over a mandatory frequency (124.8 MHz) and monitor that same frequency for situational awareness of other air traffic.

At 12:56, the DJI M210 took off for its second flight. The pilot, who was watching a flat-screen tv displaying the drone feed, took the drone up to 400′ AGL.

The pilots in the Cessna, meanwhile, were scanning for other aircraft as they began their approach toward the runway. They made a radio call with their intentions to land at 12:57. When the drone reached 400′, it was put into a stationary hover.

But that hover, unfortunately, was directly in the flight path of the Cessna. The report notes that a stationary black object, when viewed against urban clutter, would likely not have stood out to the pilots. When the aircraft was approximately 1.2 nautical miles from the airport, traveling at about 65 knots (120 km/hour), it impacted the drone at 13:01.

The Cessna landed without incident. But upon exiting the aircraft, this damage to the cowling was observed. There was also a slight scratch on the propeller.

Police Drone Collision

And the drone?

 Well, it was pretty much destroyed – as shown in this Transportation Safety Board photograph of the pieces that were recovered:

Police Drone

Other factors

 

The DJI drone was equipped with an Automatic Dependent Surveillance-Broadcast (ADS-B) receiver. These pick up signals from ADS-B equipped aircraft in the vicinity, and issue a warning to the drone pilot. The Cessna was not equipped with an ADS-B unit, however, so no warning would have been generated.

The Report says the drone pilot was monitoring the airport’s Mandatory Frequency during operations, using a handheld VHF radio. The drone pilot also had his Restricted Operator Certificate with Aeronautical Qualification (ROC-A), allowing him to operate an aviation radio. Unlike the pilots in the Cessna, drone operators are not required to broadcast their intentions when in controlled airspace. In fact, NAV CANADA does not encourage RPA pilots to broadcast on those radios, as it can contribute to clutter on the airwaves.

But the report does point out an additional key responsibility for Remotely Piloted Aircraft operators:

RPA operators are required to receive authorization from the provider of air traffic services (ATS) to operate in controlled airspace (see section 1.17.2.1). The request for this authorization must include contact information for the pilot, and “the means by which two-way communications with the appropriate air traffic control unit will be maintained.”

When authorization is granted from ATS, a telephone number for the relevant ATC unit is included in the authorization. This telephone number is to be used in case of an emergency or loss of control of the RPA. This exchange of contact information between RPA pilot and ATS is meant to satisfy the Canadian Aviation Regulations (CARS) requirement that two-way communication be maintained.

Flying a drone in controlled airspace requires obtaining clearance through NAV CANADA’s NAV Drone app. If the operation looks very complex and might involve greater than normal risk, the app will bump that request for a more careful review by Air Traffic Services.

But that’s not what happened. According to the Report, the NAV Drone app was not used at all in this incident.

The pilot of the occurrence RPA was aware of the NAV Drone application and knew that the operation on the day of the occurrence would take place entirely within the CYKZ control zone, therefore requiring authorization from ATS.

Due to the nature of the police operation underway, which involved a potentially armed individual, the RPA pilot felt a sense of urgency to get the RPA airborne as soon as possible. As well, the RPA pilot had not observed any traffic in the area during the set up of the RPA and had heard no recent transmissions on the hand-held VHF radio. As a result, the RPA pilot did not request authorization.

Interestingly, investigators later tested the NAV Drone app, requesting to fly an RPA at 400′ AGL at the location where the collision had occurred. The request was denied, and the app suggested they re-submit the request with a maximum altitude of 100′ AGL – a position far less likely to have caused problems for crewed aircraft on approach.

Police Drone Collision

Role of visual observer

 

The TSB Report spends some time on this topic. It also documents what happened on that day in October. It appears that the role of visual observer was not explained to the officer that took on the role. And it also appears that officer spent most of his time looking at the video feed from the drone, rather than maintaining Visual Line of Sight with the drone itself:

During the day of the occurrence, the RPA pilot asked for another officer to be a visual observer. Although a nearby officer acknowledged the request, the RPA pilot did not confirm who, among the officers present, would assume that role, nor did he inform that specific officer what their duties or responsibilities would be. The officer was not aware of the requirement to maintain visual contact with the RPA.

The officer who was acting as the visual observer was observing the TV display for much of the time that the RPA was airborne and did not see or hear any airborne traffic, nor could he recall hearing any radio calls over the RPA pilot’s portable VHF radio.

The report also notes that the drone pilot did not use the York Regional Police’s mandatory RPAS Pilot Checklist, and instead relied on memory to prepare for the flight. It further suggests the pilot may have been ‘task saturated,’ – “restricting his ability to visually monitor the RPA and hear radio calls on the control zone’s MF and the sound of incoming aircraft, both of which preceded the collision.”

 

Some findings…

 

It is not the Transportation Safety Board’s role to find fault or blame. But it does identify contributing factors and/or causes that likely all played a role in the collision. Here are the four key findings on that count:

Police Drone Collision

“Findings as to risk”

 

The report also notes two findings under the above category. It emphasizes that what appears below does not appear to have contributed to the collision, but could lead to adverse outcomes in the future:

Police Drone Collision

Kate Klassen weighs in…

 

InDro’s Kate Klassen is a drone and airplane pilot and has about 1000 hours instructing on the same type of plane involved in the collision. She’s also very familiar with the minutiae of RPAS regulations in Canada.

Klassen read this report with great interest and noted a few useful takeaways. In particular, how it appears the apparent focus on the task – catching a criminal suspect – may have obscured what should have been standard procedures.

“Typically First Responders have established with the Air Traffic Service providers that they can do the job and inform as soon as possible, rather than following the NAV Drone pre-authorization process the rest of us follow.” she says.

“So I think it’s less that they launched as they did, and more that they didn’t have the situational awareness to operate there safely. They were perhaps too invested in getting the job done, where they figured ‘It’s not going to happen to me’, and weren’t taking advantage of all the tools at their disposal. They probably didn’t realize how risky this location was, especially to be operating at that altitude.”

 

Briefing visual observer

 

Klassen also notes that the selection of a visual observer was not accompanied by any sort of thorough briefing – which would have included maintaining Visual Line of Sight with the RPA, monitoring the radio, and listening (along with watching) for any crewed aircraft.

“I think the situational awareness piece is important,” she says. “Have the radio on the right frequency, have the visual observer actively monitoring it. It can’t be just ticking the box that you’ve assigned someone the task.”

“A more effective trained role would be explaining or ensuring they have skill to listen in on the radio and build that situational awareness of where the aircraft are. Also monitoring the sky, listening for aircraft noise. If you can hear a crewed aircraft but not see it, that’s when it’s sketchy.”

Klassen has worked with many First Responders across Canada, and understands the pressure they can be under to get a drone in the air. The challenge is to follow Standard Operating Procedures despite that pressure – particularly in controlled airspace this close to an airport.

 

InDro’s take

 

Though no one was injured during this collision, it was a serious incident. The drone could just as easily have hit the windshield, the leading edge of the wings near the fuel tanks or damaged the landing gear. Thankfully, that didn’t happen.

The Transportation Safety Board report is both methodical and meticulous. While not pointing the finger of blame, it does highlight some procedures that most certainly could have been handled better – and likely would have, were the flight not so high-priority.

Accidents and investigations should be, in our view, viewed as learning opportunities. And in this case – whether you’re a First Responder or not – there are clearly lessons to be learned.

InDro Robotics, Area X.O team up to provide high-level drone, robot training

InDro Robotics, Area X.O team up to provide high-level drone, robot training

By Scott Simmie

 

InDro Robotics and Area X.O – the R&D complex for next-gen smart mobility, autonomy and connectivity founded and operated by Invest Ottawa with an emphasis on real-world robotics and IoT device testing – have joined forces to build and operate a new test centre at Area X.O’s private facility.

It will be dedicated to drone and robot testing, demonstration and trainingwith the physical site and training modules intended to reflect National Institute of Standards and Technology, or NIST, criteria.

This type of drone training requires very precise drone piloting skills and produces a score. It’s used for high-level drone professionals, particularly law enforcement and other First Responders, extensively in the United States.

Leveraging critical new funding from the Government of Canada’s support through FedDev Ontario, the new facility at Area X.O will be the first of its kind in Canada. With instruction provided InDro Robotics, it will harness the capabilities and infrastructure of Area X.O, and create an entirely new resource for Canadian innovators and companies in a year-round setting.

Below: A rendering of the planned site. Note the caged area at rear for the safe evaluation of drones.

 

DARTT Zone

Extensive drone training…

 

The facility will offer multiple options for drone training, in addition to the new high-level course. These will include obtaining Basic and Advanced RPAS certificates, along with on-site flight reviews.

InDro already has an extensive background with training First Responders, as well as advanced commercial pilots. We’ve done this at InDro facilities and on-site for clients. And the online portal FLYY is a collaboration with Kate Klassen, one of Canada’s most respected drone instructors.

“Online instruction is a tremendous tool,” says Klassen. “But there’s something to be said for in-person, hands-on training once you’re talking about highly specialised skills.”

The facility will combine aerial and ground robotic training and testing – all in a single location.

NIST

Robots

 

It’s not just about the drones. InDro Robotics and Area X.O strive to offer training, skills development and evaluation of the capabilities of robots.

Want to learn how to teleoperate a robot? You’ll do it here.

You’ll also be able to put your robot (or one of InDro’s) through its paces. You’ll be operating on several different surfaces, feeling the difference as an operator when moving over concrete, various grades of gravel – even through sand and water. You’ll also be piloting your robot over varying types of obstacles, along with testing the ability to climb at various degrees of inclination (if you’re so inclined).

Want to pilot using a thermal camera? Or try testing autonomous detect-and-avoid and SLAM capabilities? We’ve got you covered.

“There really isn’t any other facility of this type in Canada,” says Reece. “InDro is proud to be partnering with Area X.O to bring this unique innovation to those in the aerial and ground robotics space.”

The criteria for ground robots will also follow standards that are accepted for the testing of robots themselves – as well as operators. 

Quadrupeds

The InDro connection

 

InDro Robotics has a long and respected tradition of offering training to drone professionals. We have trained police, firefighters and other First Responders on how to effectively use drones within the Canadian Aviation Regulations (CARS part IX) regulations. We’re also fortunate to have former RCMP member Brian Fentiman – who was responsible for RCMP RPAS operations in British Columbia, on staff.

In fact, Brian created the layout for the course, and believes there are two types of clients who will want to use the test facility.

“I think there are going to be manufacturers that want their product tested, as well as police departments, fire departments, First Responders, as well as any professional agency that’s using drones,” he says.

“Part of the facility will also help other companies test ground robots – navigating curbs, driveways, inclines, sand, gravel, water and more. There’s also a netted enclosure that will allow drone manufacturers to test scenarios like GPS or compass failures and flyaways. This is a safe enclosure – technically, they are flying indoors and don’t have to seek special regulatory permissions or take on additional risk.”

Brian also points out that the facility has been designed to potentially grow over time, perhaps one day including a section for training in such areas as HUSAR – Heavy Urban Search and Rescue.

For a better idea of what the initial site will look like, check out the video below.

 

Area X.O: A competitive advantage

 

Area X.O is already a one-of-a-kind facility. On any given day you’ll see robots taking advantage of the private roads and traffic lights used for Connected and Autonomous Vehicle (CAV) testing – or drones being flown to evaluate new capabilities.

The new test centre will enhance Area X.O’s capacity for testing, training, evaluation and development, in conjunction with InDro’s expertise.

“InDro Robotics is a world leader in advanced robotic and drone R&D, and one of the very first companies in Canada to be certified by Transport Canada to fly Beyond Visual Line of Sight (BVLOS),” said Kelly Daize, Strategic Market Director of Area X.O. “We are delighted that InDro is building an R&D team onsite with us at Area X.O with 20 engineers and counting.” 

“Having this world leader co-located at our private R&D facility creates an immense competitive advantage for the innovators and companies we serve,” said Rebecca Thompson, Senior Manager of Operations, Area X.O. “We are excited to build on our collaboration and put InDro’s industry leadership, technology and certified capabilities to work to accelerate the commercialization of new robotic solutions and build the pipeline of related expertise.”

Below: InDro CEO Philip Reece at Area X.O during the TCXPO event

InDro Robotics

InDro’s take

 

We’re pleased to be involved with this project – which, to the best of our knowledge – is the first of its kind in Canada.

With InDro’s background in both drone training and robotics R&D, we’re confident this will be a perfect match for our skillset.

“Flying drones professionally, and operating robots, is a skill,” says InDro CEO Philip Reece.

“We look forward to offering our services at this facility to First Responders and professional operators from across Canada on a year-round basis. Whether it’s drones or robots, we anticipate this will become the go-to site for elevating skills and testing product capabilities in a controlled environment. We’re also pleased to again be collaborating with the excellent Area X.O and Invest Ottawa teams.”

Construction on the new facility will begin shortly, with operations expected to commence by summer, 2023.