- Mortuary robots to respectfully transport the deceased, as ebola is most virulent at the time of death and immediately following death
- Reducing the number of health professionals within the biosafety labs and field hospitals (e.g., automated materials handling, tele robotics patient care)
- Detection of contamination (e.g., does this hospital room, ambulance or house have ebola)
- Disinfection (e.g., robots that can open the drawers and doors for the commercially available “little Moe” disinfectant robot)
- Telepresence robots for experts to consult/advise on medical issues, train and supervise worker decontamination to catch accidental self-contamination, and serve as “rolling interpreters” for the different languages and dialects
- Physical security for the workers (e.g., the food riots in Sierre Leone)
- Waste handling (e.g., where are all the biowaste from patients and worker suits going and how is it getting there?)
- Humanitarian relief (e.g., autonomous food trucks, UAVs that can drop off food, water, medicine, but also “regular” medicine for diabetes, etc., for people who are healthy but cut off)
- Reconnaissance (e.g., what’s happening in this village? Any signs of illness? Are people fleeing?)
Archive for the ‘Rescue Robots’ Category
On Oct 21st, CRASAR will have the first “COA Day”– a free one day hands-on workshop for agencies to help them with the COA process. CRASAR has over 20 COAs and an emergency COA for fixed and rotor craft UAS. We’ve been helping agencies on a case by case basis with the process, which has been a drain on Brittany Duncan (our fantastic graduate student and pilot in command who does the real work)– so we decided to do this as a batch process.
Contact email@example.com for the complete flyer (which we will post soon) and the agenda. Here’s a short version:
Objectives: The purpose of this workshop is to guide fire rescue, law enforcement, and other agencies through the FAA certificate of authorization (COA) and emergency COA process needed to fly small unmanned aerial systems (SUAS).
By the end of the day, participants will:
- Complete a COA for their system (or for a mock system) for flying in their jurisdiction
- Become familiar with SUAS, how they have been used, hidden costs such as manpower, maintenance, and training, and issues such as privacy
Organization: The workshop sections will generally be organized as short 10-20 minute lectures by representatives from the FAA Central Service Center and CRASAR, followed by exercises where responders will work on their COAs or on mock COAs. Participants will have pre-workshop homework so that they will have the basic information for a COA on hand. Responders can ask questions and get help either in person or through chat. The preferred form of participation is to come to College Station but there will be a concurrent webinar. Each participant who completes the workshop will receive a certificate of completion.
Free registration: Contact Kimberly@cse.tamu.edu or (979) 845-8737 by Oct. 8 for the registration materials so that we can make sure we have enough space and enough seats for the webinar. However, we will accept on-site/day-of registration.
Who should attend: The workshop is for public agencies only, industry is not permitted at this event (we will be happy to hold a separate event through the Lone Star UASC). No experience with SUAS or flying is required, the purpose is to serve as a complete introduction to SUAS for homeland security professionals. If you do not have a specific SUAS you are considering, we will have spec sheets on representative SUAS from CRASAR’s Roboticists Without Borders members.
The Colorado mudslides appear to be the Washington state SR530 mudslide writ large (4 miles long versus 1 mile long), though thankfully with a search for three people, who could still be alive versus the 43 killed in Washington state.
Mesa County is the best place in the world to have a mudslide- Ben Miller, in the Mesa County Sheriff’s office and now director of its Unmanned Aircraft Program, has been an early adopter of small unmanned aerial systems (sUAS). Under his direction, Mesa County got the first approval for an agency to fly over an entire county. His “flock” includes a Draganfly X4-ES rotorcraft (Draganfly is a Robotocists Without Borders member!) with their own version of advanced 2D/3D mosaic software that the geologists and hydrologists at SR530 found so useful. Ben also has a Gatewing and Falcon fixed-wing sUAS.
The UAS providers of the Roboticists Without Borders team (Black Swift, Draganfly, Precision Hawk, and Texas A&M) are on stand-by to assist, possibly providing a LIDAR platform and additional software. Precision Hawk and their geospatial software, of course, were the stars of our SR530 mudslide response providing an interactive 3D reconstruction of the “moonscape” in less than 3 hours of processing time on a laptop.
Black Swift has been doing some phenomenal work that could prevent mudslides and flooding- they are developing a miniature microwave radiometer package for NASA for their sUAS that can detect soil moisture– which can determine if the soil is saturated and thus about to flood or slide. The package isn’t ready yet, but think about the implications for being proactive next spring!
The size of the mudslide raises the question of the use of multiple sUAS in a divide-and-conquer strategy. There has been a significant amount of research on this in terms of optimal path planning and general coordination. I believe the University of Colorado Boulder may hold COAs by the FAA which permit multiple platforms to be in the same area at the same time– for their storm formation studies, but I could be wrong.
Please donate to Roboticists Without Borders so that team members can continue to donate their time and equipment to help responders and accelerate the adoption of the technology.
(note: this blog was referenced by New Scientist) The horrendous number of victims at the Soma mine disaster in Turkey continues to grow. We immediately reached out to Turkish officials through Dr. Hasari Celebi at the Gebze Institute of Technology as a guiding force. Less than a year ago I had given a keynote at a workshop on disaster robotics being held there by the government with Dr. Celebi as a key driving force. It was clear that there was many scientists interested in applying their great ideas to earthquake response. Unfortunately it takes time and sustained investment to create a robotics capability for handling such a tragedy and the mine disaster was too soon.
Most people don’t realize that mine disasters have been to date the most common situation for ground rescue robots. As I note in Disaster Robotics out of the 28 disasters where robots have been used or on site between 2001 and 2013, 12 (42%) were underground mine incidents. Of the four disasters where robots were on-site but could not be used, 3 (75%) were underground mine disasters- showing just how much this technology is needed.
Underground mine disasters in coal mines are especially challenging as there may be methane to cause explosions or because the mine itself catches fire which is difficult to suppress. Mine responses are challenging based on the type of entry into the mine. Dr. Jeff Kravitz at the Mine Safety and Health Administration (MSHA) is the expert on robots for underground mine disasters and we co-authored an article “Mobile robots in mine rescue and recovery” in IEEE Robotics and Automation Society Magazine that summarizes the opportunities and challenges for robots based on an analysis of deployments in the US. MSHA may have the only mine permissible robot in the world (i.e., certified not to cause an explosion in a methane-rich environment)- the V-2, an Andros Wolverine shown in the photo.
CRASAR has assisted with two mine disasters Midas Gold Mine (2007) and Crandall Canyon (2007) and was requested to assist with two others but the technology wasn’t there. The Midas and Crandall Canyon events used smaller robots, an Inkutun Xtreme loaned from the pool at SPAWAR and a Inuktun Mine Crawler that could go down narrow boreholes. We also conducted a report for MSHA on underground rescue technologies that allowed access to their use of robots at 7 other mine disasters.
Our thoughts and prayers are with the Turkish miners, their families, and the responders.
Roboticists Without Borders returned with member FIT to Washington state with platforms from CRASAR and PrecisionHawk members to order to help determine the eminent risk of loss of life to responders, as they continued to work downslope of a potential secondary mudslide or a breach in the river. Many people assume that disaster robots are just for immediate search and rescue of survivors, but this is one of many examples of where robots can protect the responders.
Our missions were collecting data for the geologists and hydrologists from the “moonscape” and toe of the river where it was impossible to manually survey due to the flooding and quicksand-like mud and couldn’t be surveyed from manned helicopters or see from remote satellite sensing due to the higher altitudes and less favorable viewing angles. These areas are next to the cliff face of the mudslide and not in the victim recovery area.
We flew the AirRobot 100B platform under an emergency COA from the FAA on April 23 but the high winds in the narrow canyon prevented us from flying on the 24th. The PrecisionHawk was not granted an emergency COA, but we used the PrecisionHawk software to do 2D tiling of imagery and to create interactive 3D reconstructions which I will post soon (it’s finals here at Texas A&M). Brittany Duncan and I collected about 33GB of data in 48 minutes of flight time covering 30-40 acres with the CRASAR AirRobot and then about 3 hours of post processing on a laptop by the PrecisionHawk team (Tyler Collins and Justin Kendrick). Getting this type of data for ESF#3 and ESF#9 functions often takes days– now it can be done by them on demand. This is revolutionary!
FIT has a press release here and I’ll be posting photos and snippets. Big shout out to FIT who helped support the mission with both personnel on-site (Frank Sanborn and Tamara Palmer) and with partial funding.
Speaking of funding– our deployment war chest is empty. CRASAR pays for travel, PPE, etc. whenever possible for our volunteers, breakage and software upgrades, and this drained the last of our funds. We’re setting up online donations so that you can join RWB as a funding provider and donate to the cause!
Just returned from the Oso, WA, mudslides with the Field Innovation Team (FIT) but didn’t fly due to drone privacy concerns from Snohomish county. The upside is that we now have a template for manned/unmanned airspace deconfliction and can assist others in getting emergency certificates of authorization (COAs ).
We had requests from the county to fly small UAVs first thing on Thursday but it was Friday morning before we had three assets on site: two fixed wings (the Insitu ScanEagle, Precision Hawk Lancaster) and one rotorcraft (our Air Robot 100B). All of these were provided through our Roboticists Without Borders program at no cost to the county, with Insitu and Precision Hawk diverting their teams led by Kevin Cole and Pat Lohman respectively from their current jobs.
The reason for UAVs was straightforward. Responders such as WA-TF1 and WA-TF4 working on the rescue and recovery are at great risk from even a small slide or flash flooding as the river is continuously changing and ponding as the rains continue. The site itself is gooey mud and workers would have to be evacuated by helicopters hoisting them out. The canyon is narrow with trees and thus it is hard to get complete imagery from manned assets to predict landslides or manage the flooding. Geologists are gently swarming the edges of the slides setting up sensors but there is still some visual information missing. The ScanEagle and smaller Precision Hawk are world class for geospatial reconstruction and flooding. FIT had arranged for post processing of the AirRobot quadrotor imagery with new 3D reconstruction software from Autodesk. Chief Steve Mason, West Division, talks about the potential for UAVs in this article. We also got a shout out in general.
We worked with the Engineering Branch to determine flight paths and payloads to monitor the river flooding and to get 3cm per pixel higher resolution scans of the lower slide, the cliff face where geologists where having to rope themselves off to take measurements, and the “moonscape” area of the slide currently inaccessible by foot and thus the response teams couldn’t plan how to access. The team went with the Engineering Branch out to the site to refine the missions, identify launch and recovery areas, and how to maintain constant line of sight. Insitu had to pull out on the first day because we couldn’t find a satisfactory launch and recovery space within the Temporary Flight Restriction (TFR) area, which is airspace over the incident.
The need for the manned helicopters to fly at a moments notice for emergency evacuation combined with regular manned missions and the narrow canyon presented some challenges. Manned helicopters are extremely vulnerable when flying at low altitudes, and even a large bird can take them down, see the article about a near miss. That’s why a TFR is set up and it automatically bans any aircraft including UAVs operating under hobbyist rules. Everything has to be coordinated through the Air Branch of the incident.
The Air Branch instead of just saying “no” to UAVs did the opposite—they welcomed us and did a fantastic job of coordination, with Bill Quistorf helping us create a jargon-free airspace deconfliction plan that should work for just about any incident. Randy Willis and Mark Jordan at the FAA stayed on call through out the weekend working on the emergency COAs for each platform. Chief Harper gave us a room in the Oso Community Center next to the Oso Fire Station to stage in and we were touched by the generosity and community spirit of everyone we met.
However, as the Operations Branch put in the formal request for the finalized missions and we got ready to fly late on Saturday, Snohomish County Emergency Management in Everett stepped in and blocked the request. After discussions on Sunday, the new Incident Commander Larry Nickey cancelled the missions based on concerns about privacy. The families were already worried about the media leaking photos and some were very contentious about drones. It was at that point that I recalled that Washington state has some of the most restrictive drone anti-privacy laws in the country, so there is already distrust in general. There was no way for the Engineering Branch to determine without flying the UAVs if the data would be sufficiently better than what they were getting now and would significantly increase the safety of the responders to justify overruling the families. This just wasn’t the time to go into the chain of custody of the imagery or that these were no different than imagery than from the unmanned systems; the families in their grief can’t hear and the EOC personnel shouldn’t be distracted continuing to push for activities that make the families uncomfortable. Larry made the tough, but understandable, call to cancel the missions, but left the door open for flights after victim recovery was complete and the activity was cleanup and reopening the area.
This was the first outing of Roboticists Without Borders with FIT. FIT is lead by Desi Matel-Anderson, former Chief Innovation Advisor for FEMA, Rich Serino, former FEMA Deputy Administrator, and Tamara Palmer, former Program Specialist with FEMA’s Recovery Directorate, to help communities get innovations that they may not be aware of or know how to access. FIT staff worked to understand the needs of local officials and connect us with Autodesk. Frank Sanborn served as the FIT coordinator for us and he and Stacy Noland get big shout outs for helping with everything from lugging gear and driving 120 miles on Sunday between Everett, the EOC, and the site to try to get the mission request unstuck.
We are disappointed that we can’t help out but our hearts and prayers go out to the families and all of the fine people working this very, very tough event.
It doesn’t appear that small ground rescue robots are being used to assist in the search and rescue of the terrible East Harlem building collapses-if you know of any being used please let me know. We offered our robots to DHS the same day and also New Jersey Task Force 1 and the New Jersey UASI team have small robots that they used in the 2010 Prospect Towers parking garage collapse. All of our thoughts and prayers go out to the families of the 7 victims and missing- as well as to the responders working their way through this disaster.
Ground robots have been used 8 times between 2001 and 2013 for search and rescue in structural collapses- crawling underground in building collapses and mine disasters since the 9/11 World Trade Center collapse. For building collapses shoeboxed sized robots such as the Inuktun VGTV are a popular choice because that are small and the power/communications tether serves as a belay line for lowering the robot. Ground robot have video cameras but can often be outfitted with a thermal camera. The thermal camera is useful for looking for heat signatures of possible survivors and also smoldering fires or live electrical outlets. A robot typically needs both because thermal radiation produces a fuzzy image, not always good for navigation or for structural assessment. We’ve often velcro-ed a thermal camera to a robot and run a separate tether.
Gas leaks are similar to mine explosions in that there is a worry as to whether the electronics of the robots will set off another explosion. The is referred to as whether the robot is “intrinsically safe.” There are different standards for intrinsically safe depending on the industry so that makes it harder for a robotics company to create a certified explosion proof robot. I know of only one robot that is certified as intrinsically safe- the Mine Safety and Health Administrations very large “sumo” V2 robot, a variant of the Remotec Wolverine.
My book Disaster Robotics (MIT Press, Kindle, and iBook) covers structural inspection, documents 16 cases where robots have been used for structural inspection after disasters (the majority by CRASAR, but I’ve documented all cases I can find reported through April 2013) and has criteria for choosing what robot, what the different work envelopes are, lots of tables/figures per modality, and failure taxonomy and rates.
Here’s a quick guide to structural inspection in Disaster Robotics
- Chi1 defines structural inspection tasks versus recon and other tasks identified for disaster robotics.
- Ch2 list of robots used for what incident, formal failure taxonomy; this gives an overview of the 16 cases where robots have been used for structural inspection
- Ch3 use of ground robots for structural inspection, environments/work envelopes, describes the 5 cases where UGVs used for structural inspection, formulas for how to size a robot for an inspection task and a set of design spaces, gaps
- Ch4 use of UAVs for structural inspection, environments/work envelopes, describes the 7 cases where UAVs have been used for structural inspection, choice of rotorcraft versus fixed wing, conops, human-robot ratio and safety, issues with lots of GPS, gaps
- Ch5 use of marine vehicles for structural inspection, environments/work envelopes, describes the 4 cases where UMVs have been used for structural inspection, the need to inspect upstream not just the bridge substructure, choice of AUV, ROV, UMV, gaps
- Ch6 how to conduct fieldwork and data analysis, using structural inspection as an example
The death toll appears to be horrific in the wake of the Super Typhoon Yolanda– we are getting inquiries as to assistance. Our thoughts and prayers go out the victims and their families.
UAVs, if on site, can provide immediate damage assessment and locate pockets of trapped survivors as well as the best transportation routes. However, if manned aircraft are available, coordination of airspace may be difficult and manned assets will generally wave off if they see an unknown UAV no matter how low or small in the area they are working in.
UMVs– water based robots- may be of great help for searching for submerged victims and determining the state of bridges, seawalls, polluting debris, etc. While this does not help with life saving, it can enormous economic impact. Initially, ROVs and unmanned surface vehicles (boats) have advantages over AUVs (underwater robots)– AUVs can’t detect the debris in the water, whereas ROVs are on a tether and USVs work on the surface. We used ROVs for the Japanese Tohoku tsunami with our partners at the International Rescue Systems Institute and greatly speed up the reopening of a key fishing port.
The tone and content of the discussion of the lack of use of UAVs in the Colorado flooding among the community bothers me. I have flown small UAVs (or UAS depending on what agency is involved) at Hurricane Katrina and Wilma and have assisted with the UAV flights at Fukushima. I have also been turned down by the FAA for emergency COAs. I was involved in discussions to use UAVs at the Moore, Oklahoma, and the decision not to use them there.
So I feel I have unique perspective from both sides of the coin.
During a disaster, a UAS requires an emergency COA from the FAA, not FEMA. An agency or responsible party has to want to use the UAS, be it FEMA, a task force, or a sheriff before the FAA considers the request. If I as director of CRASAR ask the FAA, they would laugh at me; instead I make the request with the agency that CRASAR is working for (we don’t self-deploy which is illegal and unethical). The FAA can turn around an emergency COA in 30 minutes if the requestor can show that the UAS has an existing COA, can specify where it will fly, and show need.
Manned and unmanned aircraft are currently not allowed to operate over the same area at the same time, even though they may be at different altitudes. So if an agency wants to fly manned vehicles, such as CAP or manned helicopters trying to airlift people out, they have to decide if they want to stop those operations temporarily to let unmanned systems in. And remember, since communications with the air traffic controllers who are working the disaster and the actual pilots is spotty, there has to be a bit latency/down time to get the word out. So this could shut manned operations down in an area for quite a while. The current solution is to partition the space, e.g., “this canyon on Thursday will be just for unmanned systems.” Within that area and time frame, responders can use a small UAS on demand- though there’s always a provision to land immediately if an manned system enters the airspace for some reason.
However, having to plan to this level of detail, combined with the latency, will drive an agency such as FEMA to say it’s just not worth the time and effort- the cost-benefit to the _larger_ operations isn’t there. The cost of the deployment has never been an issue, free or not- it just may not be useful. That’s what happened at Moore. There were manned assets meeting at least the minimum needs of the responders. UAS may have provided better info, cheaper (also free in that case) but it’s a hard sell to shut down something that’s working during a disaster to use something new. The FAA was in no way a problem or obstacle, it was a FEMA decision that it wasn’t worth it. And I can understand that decision.
I think most people don’t understand why an area has to be “sanitized” of manned vehicles for a small UAS to be used at altitudes significantly lower than a manned aircraft would fly at. One reason is that the manned aircraft may indeed be flying very low, like a helicopter lower a collar to lift a person out of flood waters. That is extremely dangerous-no-room-for-surprises-or-there’s-a-crash-and-everyone-dies operation. So if tactical rescue is a possibility, you don’t want anything even nearby that could cause a problem.
I also think that the hobbyist versus public aircraft issue is poorly understood. Due to the quirk of the 1960s when dad (I never saw a mom on these outings) would take the kids, a picnic lunch, and the dog to a field to fly a RC plane, hobbyist got special regulations. Fast forward 50 years and these regulations are letting untrained people fly over crowds with open rotor ‘copters that have not been in any realistic way been tested. Yep, that loophole needs to be closed in an appropriate way. However, if the platform isn’t owned by a hobbyist, it falls under FAA regulations that require a COA. This is not necessarily a bad thing if you’ve been watching the news where ‘copters are injuring people.
But it doesn’t matter who owns what for a disaster because that airspace is totally cordoned off and hobbyist rules don’t apply. You aren’t allowed to just decide to fly your quad rotor or RC plane to help, because you are messing with the response. A manned system has to hightail it out of the area, land, and report what happened if it seems something that isn’t supposed to be in its area. So even if it seems like a good idea, the risk of interrupting a very important life-saving mission that you (or your police friend) knew nothing about is unacceptable. There’s a low risk but a high cost of failure if you interrupt the response. Self-deploying is bad, bad, bad.
Is the current system non-optimal? Definitely! Am I a happy camper? Not particularly. Do I understand why an agency might just say no? Yep. But I urge everyone to be aware of the rules and play by them. I don’t want to be trapped in a flood with a basket being lowered down to me and then the helicopter waves off, leaving me there for hours.