Lumipad
Register

When something goes wrong.

Most missions go fine. Some don't. This page is the reference for the rare-but-real moments where calm response matters most — a sudden link loss, a drone in the trees, an injured bystander, a battery beginning to swell. The procedures below are calibrated for cohort default operations: small drones, agricultural surveys, rural Mindanao contexts where the nearest hospital may be 90 minutes away. Every section is structured for fast lookup; you don't read this in order, you find the situation you're in.

Version 1.0 · Updated 05·2026 Author: Lumipad Engineering License: CC-BY-SA-4.0 Languages: EN · TL · CEB

A reference for situations where calm matters most.

Read this page when nothing is wrong — when you have time to absorb the procedures, walk through the decision trees, build the mental shape of "what would I do if X." Reading it during an actual emergency is too late; the situation moves faster than reading speed. Cohort training includes simulated emergency drills for this reason. The page is the foundation; drill repetition is what turns it into reflex.

The page is structured by emergency category, not chronology — each section is a self-contained reference for one type of situation. Section 1 establishes the calm-response framework; Sections 2-6 are specific scenarios. The downloadable kit at the top of this page provides one-page flowcharts for each section, designed for in-field reference when the page itself isn't accessible.

Note on scope. This page covers emergency response for cohort default drone operations. It does not replace first aid training, professional medical guidance, or formal emergency services. For serious medical situations, the only correct first step is contacting local emergency services. Cohort program guidelines require operators to take basic first aid training; this page builds on that foundation, doesn't substitute for it.

Section 01 The calm-down framework before specifics

Response principles.

Before any specific procedure: the framework that makes specific procedures work. Emergencies are stressful, and stress narrows attention. Cohort default response patterns are designed to keep operators in working mental state — not removing the stress, but making sure the response happens despite it. Four principles run through every section that follows.

The four response principles:

Principle What it means Why it matters How to practise
1
People before equipment. If anyone is in danger, that comes first. The drone, the imagery, the mission — all secondary to human safety.
Most equipment can be replaced or repaired. Injuries can't be undone. The hierarchy of concern is non-negotiable.
Cohort training drills explicitly include "what if a bystander is hurt" scenarios. Practising the priority order makes it reflexive.
2
Stop, then think. When something goes wrong, your first action is to stop the current operation. Then assess. Then act.
Acting on incomplete information often makes things worse. Stopping creates space for the right action to become visible.
In flight: switch to manual mode. On the ground: stop walking, look up, assess. The pause is what makes good decisions possible.
3
Talk it out loud. During emergencies, narrate what you're doing and what you're seeing. To yourself, your team, the cooperative manager — anyone present.
Speaking forces clarity; silence allows confused thinking. Observers often see things you don't when you're focused on one problem.
"Battery is dropping fast. Switching to RTH. Drone heading home. Watching for safe landing zone." Each sentence is a commitment and a check.
4
Document while it's fresh. After the immediate response, write down what happened. Within an hour ideally; same-day at minimum.
Memory of incidents fades fast and reshapes itself. Contemporary notes are the only reliable record. The cohort incident report template (in download kit) structures this.
Phone voice memo if writing isn't possible immediately. Five sentences capturing what happened, what you did, what you wish you'd done.

The "this won't happen to me" trap

A later cohort surveyed graduates 18 months post-graduation. Ten of fifteen graduates reported at least one situation they considered a real emergency during their first year. The categories distributed roughly evenly: in-flight failures, crashes in difficult terrain, weather emergencies, equipment issues. One operator in five experienced a bystander-related incident requiring careful response.

The data is clear: emergencies happen. Operators who treat them as inevitabilities — and prepare accordingly — handle them better than operators who treat them as remote possibilities. Cohort default training includes regular emergency drills throughout the program, not as a one-time checkbox.

If you're reading this page thinking "I'm too careful for this to apply to me" — that's the most dangerous mental state. The careful operators have emergencies too; they just handle them better because they've prepared.

What "calm" actually means in this context. Cohort instructors specifically distinguish between "feeling calm" (emotional state, not always available) and "acting calm" (behavioural pattern, always available with practice). You may feel terrified during an emergency; that's human. Acting calm — speaking deliberately, moving methodically, following the procedure — is a learned skill that works regardless of internal feeling.

Practical markers of acting calm:

  • Speaking in complete sentences, not fragments.
  • Standing still or moving deliberately, not pacing or running.
  • Following the procedure step-by-step, not skipping ahead.
  • Asking for help when needed; accepting help when offered.

These behaviours can be performed even when feeling stressed. Emergency drill repetition makes them the default response; without practice, the default tends toward fragmented action. This is why cohort training drills emergencies before graduates need them.

Section 02 Drone-side failures during a mission · seconds matter

In-flight failures.

The drone is in the air. Something just changed — link quality dropped, GPS sat count dropped, a motor sounds wrong, the OSD shows an unexpected mode. You have seconds to decide whether this is "monitor closely" or "abort now". This section covers the specific failures and the response pattern for each.

The general response pattern for in-flight failures:

  1. Identify what changed. Voltage? GPS? Link? Mode? Visual contact? Name it before deciding.
  2. Take manual control if able. Switch out of mission mode to Position Hold or Angle. The drone now responds to sticks, not to the autonomous logic that may have caused the problem.
  3. Bring it back. Either fly it home manually, or trigger RTH if RTH is reliable for the current conditions.
  4. Land safely. Original launch zone or pre-identified emergency landing zone.
  5. Diagnose on the ground. Don't troubleshoot in the air; that's how mistakes compound.
Failure Symptoms Immediate action Cohort response
LINK
Lost RC link Pilot input not reaching drone. RSSI drops to zero on OSD. Drone enters RC failsafe (configured in fc-setup.html Section 7).
RC failsafe should trigger automatically: drone holds position briefly, then RTH. Pilot waits, monitors, prepares to resume control if link returns.
Don't move from your position; the link may return as you walk. Stay in radio shadow while it sorts. Most link losses recover within 5 seconds.
GPS
GPS lock lost Satellite count drops below 6. Position-hold and RTH unreliable. Drone may drift in autonomous modes.
Switch to Angle (manual) mode immediately. The drone now flies on attitude only, no GPS dependency.
Fly back manually using FPV view. Don't try to use Position Hold or RTH until lock is reacquired. Land manually in the launch zone.
VOLT
Sudden voltage drop Battery voltage drops faster than expected. Could indicate cell failure, dead cell, or wiring issue.
Trigger RTH immediately if voltage above 3.5V/cell. If already below, land at nearest safe spot; don't try to make it back to launch.
Don't fly the drone hard; reduce speed to minimise current draw. Land gently to avoid further pack stress.
MOTOR
Motor anomaly One motor sounds different (whining, grinding) or visibly wobbles. Drone may yaw unexpectedly.
Land immediately at nearest safe spot. Don't try to fly back; partial motor failure can become full motor failure with no warning.
After landing, full mechanical inspection before re-launch. Replacement motor may be needed; don't resume mission with marginal motor.
UNRESP
Unresponsive in autonomous mode Drone stops following the mission. Hovers in place, drifts, or moves in unexpected direction.
Switch to Angle (manual). The drone should respond to sticks. If no stick response, switch to Position Hold; if still no response, RC failsafe will trigger.
After recovery, don't resume the mission until you understand what caused the unresponsiveness. Diagnose on the ground.
VISUAL
Lost visual contact Pilot can't see the drone. May be due to distance, terrain, sun glare, attention drift.
Don't guess at drone position from OSD alone. Trigger RTH; the drone should return to a visible position. Pilot scans for it during return.
VLOS rule violation if not corrected promptly. Even within 500m, sun glare and terrain can hide the drone. Recover visual contact before continuing.

The "fly-away" scenario

The most concerning in-flight emergency: drone heading off in an uncontrolled direction, not responding to RC input, not returning home. Possible causes: GPS confusion + autonomous mode logic failure, severe RC interference, FC firmware bug, magnetic interference confusing the compass.

Cohort default response sequence:

  1. Try Angle mode — disables GPS dependence; the drone should respond to sticks immediately.
  2. If no response, try the throttle-cut switch — configured in fc-setup.html as the kill switch. The drone falls; this is acceptable if it's heading toward a populated area or restricted airspace where the alternative is worse.
  3. If neither response, the drone is genuinely fly-away. RC failsafe (configured for RTH) will eventually trigger when the drone exits radio range. Track its likely path; prepare to recover or report.

Fly-aways are rare but not theoretical — a later cohort saw one (firmware bug, recovered intact). The kill-switch decision is genuinely hard: dropping a drone is bad, but a drone heading toward a populated area is worse. The decision should be made before the situation arises; verbalising "I will use the kill switch if X" during pre-flight (Section 3 of field-ops.html) commits to the decision in advance.

The diagnostic-on-the-ground principle. When something goes wrong in flight, the temptation is to troubleshoot from the ground station — try a different mode, push different sticks, see if it recovers. This is how minor problems become major ones.

The cohort default: get the drone on the ground first, then diagnose. Even if "trying one more thing" might recover the situation, the cost of failure (more serious crash, longer fly-away, potential injury) is much higher than the cost of a precautionary landing. Never sacrifice a known-safe landing opportunity for a chance to recover the mission.

Section 03 The drone is down · what happens next

Crash response.

Despite all precautions, sometimes the drone goes down. The crash response procedure is about three things: making sure no one is hurt, recovering the drone safely, and documenting what happened. Different scenarios (water, dense canopy, hard ground, structures) need different recovery approaches; injury risk varies similarly.

The crash response sequence (regardless of crash type):

  1. Verify no one is hurt. Visual scan of the crash area; ask cooperative members if anyone was nearby. If injury suspected, see Section 4 (bystander emergencies).
  2. Disconnect power if accessible. Even a crashed drone can have ESC/motor activity if the FC is still powered. A still-powered LiPo in a crash is also a fire risk (Section 5).
  3. Document the scene. Photos of the crash site before moving anything. The wreckage location, orientation, surrounding terrain. Useful for post-incident analysis and for cooperative records.
  4. Recover when safe. Different terrain types have different recovery procedures (below).
  5. Notify cooperative leadership. Honest brief explanation of what happened. Don't hide it; cooperatives respect honesty about problems.
Crash type Specific recovery Risk factors Equipment outcome
HARD
Hard ground crash Drone hits cleared field, road, or open ground. Most common crash type for cohort default operations.
Walk to crash site; disconnect battery; gather all parts (props often scatter several meters). Recover wreckage to truck for full assessment.
Low secondary risk — open terrain is safe to walk on. Watch for hot motors briefly; LiPo damage check on-site before transport.
Often repairable — cohort default crash repair ~₱2,000-8,000 in parts (props, motor, possibly arm) and 2-4 hours of work. See repair.html (proposed).
CANOPY
Tree / dense canopy Drone caught in branches, possibly suspended above ground.
Don't climb the tree. Cooperative members may know local approach (long pole, ladder, eventual deliberate fall). Mark location; return with appropriate equipment if needed.
Climbing risk is real and unnecessary. Drones suspended in trees often fall on their own within hours. Equipment damage from delay is recoverable; injury from a fall is not.
Often recoverable but variable — props usually destroyed, motors and frame may survive. Branches can damage propellers and arms.
WATER
Water crash Drone in pond, irrigation channel, river, or rice paddy.
Recover ASAP if shallow water (under 1m). Don't wade into deeper water; drowning risk exceeds equipment value. Cooperative may have local knowledge of safe approach.
Submerged LiPo is a fire risk after recovery — heat from chemical reaction. Disconnect immediately; place in fireproof bag; expect possible swelling.
Usually destroyed — water shorts the FC and ESCs. LiPo may be damaged. Total loss likely; salvage frame and motors at best.
STRUCT
Structure / building Drone hits wall, roof, or other structure. May have caused property damage.
Recover the drone with property owner's permission. Inspect structure for damage; document with photos. Address damage with property owner before leaving.
Property damage liability is real. Address it openly; offer to pay for repairs. Insurance documentation may apply (Section 6).
Variable — hard impact often destroys frame; soft impact (hit fabric awning, then fell) may leave drone repairable.
REMOTE
Crash in inaccessible terrain Cliff face, dense forest beyond walking access, distant from any path.
Mark GPS coordinates of last-known position from telemetry log. Discuss with cooperative whether recovery is feasible; if not, accept loss and document for incident report.
Don't pursue recovery in dangerous terrain. ₱25,000-50,000 of drone is not worth a serious injury or fall. Lost drones are an operational reality.
Lost or unrecoverable — accept and document. The replacement cost is the cost of the lesson.

The "should I keep flying today" decision

After a crash, the question of whether to continue the day's missions arises. Default cohort answer: no. Reasons:

  • Equipment confidence: even with a backup drone, the cause of the crash is often unclear immediately. Resuming with potentially-related conditions risks a second crash.
  • Operator state: a recent crash affects judgment. Even calm operators take time to reset; flying with degraded judgment is how second crashes happen.
  • Cooperative relationship: the cooperative just witnessed something going wrong. Resuming immediately can feel reckless to them; rescheduling demonstrates care for the relationship.

Exceptions exist: minor crashes with clear causes (prop strike from a bird, hard landing in cohort default conditions) and confident operators sometimes continue. But the default — stop flying for the day after any crash — is the cohort recommendation. The mission gets rescheduled; the relationship and equipment stay intact.

If the crash was during a paid mission: the cooperative is paying for survey work that just got disrupted. Cohort default approach to communicate this:

  • Honest acknowledgment: "I had a crash; the equipment is damaged; I won't be able to complete today's mission."
  • Specific make-good: "I'll return with replacement equipment within X days at no additional cost. The original mission scope and pricing will apply."
  • Documentation: provide a brief incident note within 24 hours so the cooperative has it for their records.
  • No defensiveness: don't blame conditions, equipment, or anything external. The cooperative invited you; the equipment is your responsibility.

Later cohorts have examples of graduates whose handling of a crashed-mission situation strengthened the cooperative relationship: the cooperative observed honesty and professionalism under pressure, which is rare and valuable. The crash itself was the smaller event compared to the recovery handling.

Section 04 When people are involved · highest-stakes category

People and bystanders.

Most cohort emergencies are equipment-only — no one is hurt; the worst case is replacing a drone. Some emergencies involve people. This section is the most important; getting it right matters more than any other emergency category. The procedures below cover injury response, hostile encounters, and animal incidents.

Important context

The procedures below are for cohort default operations and do not replace formal first aid training, professional medical guidance, or emergency services. Cohort program guidelines require operators to maintain basic first aid certification (PRC-recognised programs); this page builds on that foundation. For any serious injury, contacting local emergency services is the only correct first step. The Philippine Red Cross national hotline is 143; barangay-level emergency contact should be confirmed during pre-mission setup (Section 2 of field-ops.html).

Bystander injury from drone:

  1. Stop all flying immediately. Land any drone in the air; secure all equipment. The mission is over.
  2. Get to the injured person quickly but calmly. Running can cause additional injury or panic; walking with purpose is the right pace.
  3. Assess the injury. Use whatever first aid training you have. Don't move the person if neck/back injury is possible; let medical professionals make that call.
  4. Call for help. Cooperative manager often has barangay-level contacts. The barangay captain or local health worker may be the closest medical resource. Philippine Red Cross 143 for serious situations.
  5. Notify cooperative leadership immediately. They need to know to support response and inform local authorities if appropriate.
  6. Stay with the injured person until help arrives. Don't leave them alone; ensure transport to medical care is happening.
  7. Document afterwards, but not before care is in hand. The incident report comes after the person is safe and being treated.
Situation Immediate priority Cohort response What not to do
PROP
Propeller cut Bystander injured by a spinning propeller, typically during arming or near a launch zone.
Disconnect drone power immediately. Apply direct pressure to bleeding wounds with cleanest cloth available; elevate if extremity. Get medical help.
Most propeller cuts on cohort default 5"/7" builds are minor (under 5cm, shallow) but bleed heavily. Apply pressure; the bleeding looks worse than it is.
Don't restart the drone; don't resume flying. The mission is over for the day. Don't under-report severity to "save the mission."
IMPACT
Impact injury Drone struck a bystander during flight or fall. Visible injury or possible internal injury.
Don't move the person if head/neck/back impact possible. Cover with a clean cloth; keep them still and warm; call for emergency services.
For visible head injuries: medical assessment is essential even if person seems okay. Concussions can be subtle.
Don't attempt complex first aid beyond your training. Don't move someone with possible spinal injury. Don't let the person walk it off.
EYE
Eye injury Debris from prop strike, fragment from crash, or direct prop contact near eye.
Cover the affected eye with a clean cloth or eye patch. Don't rinse, don't apply pressure, don't try to remove anything from the eye. Get to medical care quickly.
Eye injuries are time-sensitive. The affected person may need ophthalmologic care within hours, not days.
Don't rinse the eye unless instructed by medical professional. Don't push on the eye to "examine" it.
PSYCH
Psychological distress Bystander shaken or panicked from near-miss, witnessed crash, or general drone fear. No physical injury.
Stay calm; speak slowly; sit with them. Acknowledge that what happened was scary. Don't dismiss their reaction.
Allow time. Don't rush to "get back to work." The cooperative relationship benefits from genuine concern; suffers from minimization.
Don't tell them they're overreacting. Don't resume drone operations near them without explicit consent. Don't make it about you.

Hostile encounter or refused access

Occasionally, someone (not part of the cooperative) confronts the operator about drone activity — concerned about privacy, surveillance, or perceived intrusion. This is rare in cohort agricultural contexts but worth being prepared for.

Cohort default response:

  • Stop flying. Land the drone immediately; don't continue while the situation is unresolved.
  • Speak respectfully. Acknowledge the concern; explain the work briefly and honestly. "We're doing a survey for the cooperative manager [name]; we're not photographing private property; happy to show you what we're capturing."
  • Get cooperative leadership involved if the situation persists. The barangay captain or cooperative manager has standing the operator does not.
  • Be prepared to leave if the situation can't be resolved. The mission can be rescheduled; an escalating confrontation cannot be undone.
  • Don't engage aggressively, ever. Even if the other party is wrong about the work being intrusive, escalation serves no one.

Documentation matters here too. Write down what happened, who was involved, how it resolved. This becomes part of the incident record (Section 6).

Animal incidents are a less-discussed category but happen. Most often: aggressive dog approaching the operator or a working drone area. Less common: livestock spooked into stampede; raptor attacking the drone in flight (carabao egret, sea eagle).

Practical responses:

  • Aggressive dog: don't run. Stand still, avoid eye contact, speak calmly. Cooperative members usually know the dog and can call it back. Most farm dogs are protecting their territory rather than attacking; backing away slowly resolves it.
  • Spooked livestock: prioritise getting bystanders to safety. Don't try to control livestock; cooperative members know how. Land the drone away from the stampede path.
  • Bird attack on drone: rare but documented. Land if possible; the bird is defending territory. Continuing to fly while attacked usually causes a crash (and may injure the bird).

A later cohort had one bird-attack incident (sea eagle in coastal cooperative) that ended in a controlled landing. No injury to bird or drone. The lesson: birds defend their territory from drones; surveys near eagle territory benefit from local intelligence about active nests.

Section 05 Rare but serious · LiPo-specific procedures

LiPo fire response.

LiPo batteries can fail catastrophically — swelling, smoking, or igniting. The chemistry is different from regular fires; standard fire response is wrong. This section covers LiPo-specific response: prevention, recognition, containment, and what to do (and not do) if a LiPo ignites. Cohort default operations have not had a LiPo fire incident; the procedures here are precautionary.

LiPo failure stages — what to watch for:

Stage Signs What to do Risk level
1
Swelling (puffing) Pack visibly larger than normal; sometimes bowed or warped. May feel slightly warm.
Disconnect from charger or drone. Move to fireproof bag. Place outside or in concrete-floored area; don't store with other equipment.
Low-medium. Pack should not be used; should be discharged safely and disposed of.
2
Heat without visible damage Pack noticeably warm to touch, especially after a flight or charge. Voltage may also be irregular.
Don't use the pack. Move to fireproof location, monitor for 2-3 hours from a safe distance. Don't touch repeatedly.
Medium. Pack may stabilise or progress; monitor before disposal.
3
Smoking Wisps of smoke from pack; chemical smell. May be accompanied by hissing.
Move people away. If safe to handle (gloves, tongs), move pack outside to clear ground area. Otherwise, evacuate the area and let it run its course in place.
High. Pack may ignite; nearby items at risk. Monitor from distance; have water and sand nearby.
4
Active fire (flames) Pack ignites with visible flame; rapid temperature rise; possible cell ejection.
Evacuate the immediate area (~10m radius). Use sand, dry sand-based extinguisher (Class D), or large amounts of water to cool surrounding materials. Don't try to put out the LiPo itself — let it burn out; cool the surroundings.
Severe. Risk to people, equipment, and structures. Call emergency services if fire spreads to other materials.

Why standard fire response is wrong for LiPo

LiPo battery fires are chemical reactions, not simple combustion. The pack contains its own oxidiser; smothering with a typical fire blanket doesn't starve it of oxygen the way it would with a wood fire. Water can help cool the surroundings but doesn't extinguish the cell reaction itself.

Specific things not to do:

  • Don't use a CO₂ extinguisher — doesn't affect LiPo chemistry.
  • Don't use a foam extinguisher — same; LiPo is self-oxidising.
  • Don't pour water directly onto the burning pack — water won't stop the reaction and can cause electrical hazards if pack is connected.
  • Don't try to move a burning pack with bare hands — can cause severe burns and ignite clothing.

The right approach: let the LiPo burn out in place; cool surrounding materials to prevent fire spread. Sand is the most reliable cooling agent; large amounts of water can work for surrounding objects but not the LiPo itself.

Prevention is the main defence. LiPo fires are rare in cohort default operations because the prevention is simple:

  • Always charge in fireproof bags. Cohort default: ~₱600 LiPo bag; replace every 6 months or after any heat event.
  • Never charge unattended overnight. Charge during the day when you're present.
  • Never charge a damaged or swollen pack. Swollen packs go to disposal, not to charging.
  • Storage at correct voltage (3.85V/cell). Storing at full charge for extended periods is the leading cause of swelling.
  • Cycle tracking: retire packs from mission work after ~70-80 cycles or any heat/swelling event.
  • Inspect every pack before use: look for swelling, soft spots, or unusual heat. Damaged packs go to disposal, not to flight.

The cohort field bag includes: one LiPo bag for charging, one separate "discharged" bag for spent packs, sand or fire blanket for emergency response. Total cost ~₱1,500. Worth every peso.

LiPo disposal

Damaged or end-of-life LiPo packs need correct disposal. The cohort default workflow:

  1. Discharge to zero: connect to a high-resistance load (a pair of 12V automotive bulbs work) until voltage is below 1V/cell.
  2. Submerge in salt water: 5L of water with 200g salt; submerge the discharged pack for 24+ hours. Chemistry stabilises.
  3. Dispose with general waste: cohort default is brought to a Davao recycling centre that accepts batteries; barangay disposal is acceptable for emergencies.

Don't throw an undischarged or damaged LiPo into general waste — it can ignite during transport or at the disposal site. The discharge-and-saltwater process makes the pack safe for normal disposal.

Section 06 After the immediate response

Post-incident protocols.

The immediate emergency is over. The drone is recovered, the injury is being treated, the LiPo is disposed of safely. The post-incident phase is about documentation, reporting, and learning. This section covers what to record, when to notify authorities, and how to ensure the incident becomes a learning event for the cohort and partner orgs.

The post-incident sequence:

Step What to do Timeframe Why
1
Immediate documentation Capture facts while fresh: what happened, when, where, who was present, what conditions were like, what response was taken.
Within 1 hour ideally; same-day at minimum
Memory degrades and reshapes itself within hours. Contemporary notes are far more reliable than reconstructions a day later.
2
Cooperative notification Provide written incident summary to cooperative leadership for their records. Brief, factual, no defensiveness.
Within 24 hours
Cooperatives need this for their internal records and any follow-up. Volunteering it builds trust; making them ask diminishes it.
3
CAAP reporting (when required) Some incidents require CAAP notification. Generally: any incident involving injury to a person, significant property damage, or airspace violation.
Within 72 hours typically; same-day for serious incidents
Reporting requirements depend on operation type and incident severity. See safety.html for the regulatory framework. When uncertain, consult CAAP or report.
4
Insurance documentation If insured (recommended for partner-org operations), submit claim with photos, witness statements, and incident report.
Within insurer-specific window (typically 7-30 days)
Documentation gathered immediately is more useful than memory-reconstructed reports weeks later.
5
Cohort or partner-org incident log Add to the graduates Slack incident channel (or partner-org equivalent). Anonymised if needed; full detail among trusted graduates.
Within 1 week
Other operators learn from your incident. The cohort's collective wisdom on emergencies grows from these shared records.
6
Personal review and adjustment Reflect on what happened, what you'd do differently, what training would have helped. Update your personal protocols.
Within 2 weeks (after emotional processing time)
Without explicit reflection, the lessons fade. With it, the same operator handles similar situations differently next time.

When CAAP reporting is required

CAAP's reporting requirements for drone operations are evolving; this is a snapshot rather than authoritative guidance. Cohort default approach: when in doubt, report. Over-reporting is a minor administrative issue; under-reporting can be a serious regulatory problem.

Generally requires reporting:

  • Injury to any person caused by drone operation (any severity)
  • Significant property damage from drone (e.g., damage to a structure, vehicle)
  • Airspace violation (entry into restricted zones, altitude violations)
  • Drone lost or unrecovered
  • Mid-air encounter with another aircraft (any type)

Generally does not require reporting:

  • Self-only drone crash with no other involvement (still document internally; not CAAP-reportable)
  • Minor LiPo swelling without fire
  • Mission abort due to weather or equipment with safe landing

For specific guidance, see safety.html and CAAP's current circulars. Cohort engineering is happy to advise on grey-area cases via the graduates Slack workspace.

The cohort incident record. Cohort engineering maintains an anonymised incident log accessible to current cohort members and graduated graduates. The log includes:

  • Incident type and category (cross-referenced to this page's sections)
  • Brief description of what happened
  • Response taken and outcomes
  • Lessons learned and adjustments to cohort default procedures

The record is the cohort's institutional memory. It's what makes individual incidents — which would otherwise be private learning experiences — into program-wide improvements. Contributing your incident report is one of the most valuable things you can do for the cohort's long-term safety.

Personal incident log. Beyond the cohort record, graduates typically maintain their own incident log: every situation they considered notable, including near-misses that didn't become incidents. Reviewing this log periodically (monthly, quarterly) reveals patterns: types of conditions that lead to issues, equipment behaviors to watch for, recurring decision points. Personal pattern recognition is the deepest form of learning.

Emotional processing. Serious incidents — especially those involving injury or near-injury — affect the operator emotionally beyond the immediate response. Cohort experience is that:

  • The first 24-48 hours are often shock; technical learning is limited.
  • The first week brings replay, doubt, and sometimes avoidance of flying.
  • 2-4 weeks brings calmer reflection and useful pattern extraction.
  • 3-6 months brings full integration into the operator's mental model.

Allowing this processing time is part of professional emergency response. Pushing back into operations too quickly often produces second incidents; taking time for processing produces better operators long-term. Cohort culture explicitly supports time off after serious incidents; partner orgs are encouraged to do the same. Alumni Slack has channels for incident discussion among trusted peers, which many graduates find helpful.

Six numbers across emergency response.

Reference values for emergency thresholds, response timing, and equipment costs. Useful for calibrating expectations and budgeting prevention.

~3 sec
In-flight decision window
Time from anomaly to abort decision
143
PH Red Cross hotline
National emergency contact
10 m
LiPo fire safety distance
Evacuation radius for active fire
~₱8,000
Typical crash repair
Cohort default 5" build, recoverable
~70 cycles
LiPo retirement threshold
From mission work; training-only after
72 hr
CAAP reporting window
For incidents requiring notification

Four cases from cohort and partner-org operations.

Specific situations from cohort 02 and 03 records, plus partner-org incidents, illustrating how emergency response played out in practice. Each is anonymised but reflects real incidents.

"The fly-away that wasn't."

Later-cohort alumna, year 1 post-graduation

Mid-mission, the drone began drifting away from the AOI in autonomous mode. The alumna's training kicked in: switched to Angle mode within 4 seconds; drone responded immediately. Diagnosis on the ground: GPS module had developed a loose wire causing intermittent position errors. The 3-second decision window held; what could have been a fly-away became a 30-minute repair. Lesson: practised emergency response prevented a serious incident from developing.

"LiPo swelling caught at pre-flight."

Partner-org operator, large rice cooperative

Pre-flight inspection revealed slight pack swelling on a 35-cycle battery. The operator removed it from rotation, completed the day with remaining packs, then disposed of the swollen pack via the saltwater protocol that evening. No fire, no injury. The pack would likely have failed during flight if used; the inspection caught it. Lesson: pre-flight LiPo inspection earns its keep regularly. The 30 seconds of checking each pack prevents the rare-but-serious fire scenario.

"Bystander concerned about surveillance."

Current-cohort graduate, mid-Mindanao cooperative survey

A neighbor of the cooperative approached during mid-mission, concerned the drone was surveilling his property. The graduate landed immediately, walked to the neighbor with the laptop showing live captured imagery (only the cooperative's field), explained the work, offered to show him exactly what was being captured. The neighbor relaxed within ~10 minutes; the cooperative manager joined and reinforced. Mission resumed after 30 minutes. Lesson: hostile-encounter response works when it leads with respect and transparency. Defensiveness would have escalated.

"Crash recovery that strengthened the relationship."

Later-cohort alumna, recurring partner cooperative

Drone crashed during a recurring monthly survey — gusty wind exceeded the alumna's ability to maintain control of an aged 7" build. She landed in a cleared field, no injury, drone substantially damaged. Honest debrief with cooperative manager: explained the cause (build limitation in unexpected wind), offered free re-fly the following week with a fresh build. Cooperative was unfazed; expressed appreciation for honesty. The recurring contract continued without disruption. Lesson: honest handling of failure can strengthen rather than damage a working relationship.

Questions worth answering carefully.

How do I drill emergency response if it rarely happens for real? +

Cohort default training includes simulated emergency drills throughout the program. Specifically:

  • Simulator-based drills: simulator.html Section 4 (the exercise library) includes B1-B4 — drone facing pilot, wind, motor failure, GPS dropout. Run these regularly, not just during training.
  • Verbal walk-throughs: with cohort cell or graduates group, talk through specific scenarios. "What would you do if X happened right now?" — without actually flying. Builds the mental model.
  • Pre-mission scenario rehearsal: before each mission, mentally run through the abort triggers and what you'd do. Takes 2 minutes; primes the response patterns for the day.
  • Post-incident review: when an incident occurs (yours or another graduate's), discuss it. The shared learning makes everyone's response better.

The skill atrophies without practice. Operators who haven't drilled in 6+ months perform measurably worse in real emergencies than those who drill quarterly. Building the practice into the rhythm of operations is the cohort default.

What if I'm alone when an emergency happens? +

Solo emergencies are harder. Cohort default discourages solo flying for paid missions specifically because of this. If you find yourself solo during an emergency:

  • For drone-only emergencies: the procedures in this page work the same. Slower without observers, but workable.
  • For human-injury emergencies: call for help immediately. Philippine Red Cross 143; barangay-level contact you confirmed pre-mission. Don't try to handle medical situations alone if you can avoid it.
  • For LiPo fire: evacuate; let it burn; cool surroundings. Don't try to fight a battery fire alone.
  • Documentation: voice memo on phone if you can't write. Capture facts while fresh.

The case for not flying solo for paid missions becomes very concrete during an emergency. The presence of an observer roughly doubles the effective response capability.

Should I carry a first aid kit? +

Yes. Cohort default field bag includes a basic first aid kit:

  • Sterile gauze and bandages (multiple sizes)
  • Adhesive bandages (range of sizes)
  • Antiseptic wipes
  • Eye patches (sterile, individually wrapped)
  • Medical tape
  • Disposable gloves (multiple pairs)
  • Cold pack (instant-activate type)
  • Small first aid pocket guide

~₱500-800 total; available from any pharmacy or medical supply store. Check expiry dates annually; replace as needed.

This handles minor injuries (small cuts, scrapes from prop strikes, minor burns from hot motors). For anything more serious, the kit's job is buying time until proper medical care arrives. Don't overestimate what a basic kit can do.

Cohort program guidelines require operators to maintain basic first aid certification. The kit complements training; doesn't replace it.

When should I call my cohort instructor or graduate community? +

Earlier than you might think. The cohort's collective experience handles many situations you've never seen before. Call when:

  • Situation feels genuinely uncertain: not sure if this is reportable; not sure if equipment is safe to use; not sure how to handle a cooperative-relationship complication.
  • Emotional state is affected: post-incident processing benefits from talking to someone who understands the work.
  • Decision has long-term consequences: regulatory questions, insurance claims, partner-org communication.
  • Just want a second opinion: trusted peers are valuable for this.

The graduates Slack workspace has dedicated channels for incident discussion. Cohort engineering monitors these and responds within 24 hours typically. Partner orgs maintain their own equivalent channels.

You don't need to handle every situation alone. The cohort exists partly so individual operators have a network when they need one.

What if the drone causes property damage? +

Address it openly with the property owner; don't try to leave without acknowledgment. Cohort default response:

  • Acknowledge immediately: explain what happened; apologise sincerely; offer to address the damage.
  • Document the damage: photos, dimensions, what was damaged. Useful for repair quotes and any insurance claim.
  • Offer to pay for repairs: get a quote from a local repair person; pay the property owner the cost or pay the repair person directly. Don't try to do amateur repairs yourself.
  • Document for insurance: if you carry liability insurance (recommended for partner-org operations), file a claim; provide all documentation gathered.
  • Notify cooperative leadership: they may have local relationships that help resolve the situation; they should know what happened on their land.

Property damage is generally minor for cohort default 5"/7" builds — a broken window, damaged fence, dented vehicle. Handle it openly and the relationship usually survives. Try to hide it and the damage to the relationship is permanent.

What about insurance for cohort default operations? +

For individual graduates starting commercial work, cohort default is to start uninsured but transition to insurance as operations scale. The threshold is roughly:

  • Below ~5 paid missions per month: insurance often costs more than expected losses. Self-insure by maintaining a repair fund (~₱20,000 reserve).
  • 5-20 paid missions per month: liability insurance worth considering. Several Philippine insurers now offer drone-specific policies; ~₱5,000-15,000/year for ₱500,000-1,000,000 coverage.
  • Above 20 missions per month or any partner-org work: liability insurance strongly recommended. Some partner orgs require it for their operators.

Cohort engineering doesn't endorse specific insurers. Search "Philippines drone insurance commercial" for current options. Check that the policy covers actual cohort default operations (commercial agricultural surveys), not just hobby use. Read the exclusions carefully.

Insurance is one piece of risk management. Equipment investment, training, careful site selection, and conservative operations envelope all reduce the need to claim. The insurance is for catastrophic events; routine operations should never need it.

Should I tell the cooperative about every minor incident? +

Generally yes; specifically the cohort default is to err toward more disclosure rather than less. The threshold depends on what affected the cooperative:

  • Affected the mission (incomplete coverage, re-fly needed, delayed delivery): definitely tell them. They're paying for the work; they should know.
  • Equipment-only event with no mission impact (small crash, recoverable, mission completed): light mention is fine — "we had a minor issue with one of the props during the mission, no impact on the imagery." They appreciate transparency without you making it dramatic.
  • Near-miss with no actual impact (avoided crash, GPS warning that recovered): probably not necessary unless they observed it directly. Internal logbook record; don't alarm them about non-events.

The principle: the cooperative is your partner in the work. They benefit from knowing what's happening on their land. Information they'd want to know justifies sharing; information that would only worry them about non-events doesn't.

How does cohort culture treat operators who have incidents? +

Honestly, with support. The cohort default is that incidents are part of operational reality — no one operates for a year without something going wrong. The culture distinguishes between:

  • Incidents handled well: emergency response was prompt, honest, professional. The operator is supported; the lessons are extracted; operations continue. Often the operator earns respect for their handling.
  • Incidents handled poorly: cover-ups, defensiveness, blaming external factors when operator error was the cause. The cohort intervenes for retraining or, in serious cases, restricts the operator from paid work until issues are addressed.
  • Repeated incidents from the same operator: structured review of what's causing the pattern. May indicate need for additional training, equipment limits, or operational scope changes.

The single biggest factor in how an operator's incident is treated is how they handle it. An operator who handles a crash well — honest, prompt, taking responsibility — is in better cohort standing than one who avoids incidents through over-caution but would handle a real one poorly. The skill of handling incidents is itself valued.