CAAP RPA Controller cheat sheet

Core statute: Republic Act No. 9497 (Civil Aviation Authority Act of 2008) created CAAP and vests rulemaking, licensing, and enforcement authority; RPAS rules sit under this mandate.

PCAR Part 10.5 governs RPAS operations in the Philippines; it is read together with Part 2 (personnel licensing) and Part 8 (operations) where cross-referenced.

Registration: RPAS above the mass threshold set in Part 10.5 must be registered with CAAP and carry a registration marking; the operator retains the certificate and displays the mark on the airframe.

RPAS Operator Certificate (ROC) or equivalent authorization is required for commercial, corporate, and government operations; recreational flights by private individuals fall under lighter requirements.

Remote pilot qualification: CAAP-issued remote pilot certificate or rating, with medical fitness and knowledge/ skill assessment per Part 10.5; currency and recency requirements apply to privileges.

Beyond visual line of sight (BVLOS), night, over-people, and beyond-400 ft AGL operations require prior CAAP approval via an operations manual and risk assessment.

Record keeping: logs of flights, incidents, maintenance, and pilot currency must be retained and produced on CAAP request; accident/incident notification is mandatory and time-bound.

Enforcement: CAAP may suspend, revoke, or refuse certificates; violations can also attract penalties under RA 9497 and, where safety is endangered, criminal liability under Philippine law.

Default limit for unapproved RPAS flight: 400 ft AGL (120 m) and within visual line of sight; above this, or in controlled airspace, a clearance or approval is required.

Class A–E airspace is controlled; Class F is advisory; Class G is uncontrolled. RPAS in controlled airspace need ATC coordination regardless of mass.

Prohibited and restricted areas in the Philippines include vicinity of aerodromes (control zones and traffic areas), military installations, and designated security zones; entry requires explicit authorization.

No-fly buffers around airports: operations inside the aerodrome traffic zone or approach/departure paths are prohibited without ATC and aerodrome operator coordination.

Distance-from-people rule: do not fly closer than the prescribed lateral distance to persons not involved in the operation, and never over assemblies of people, without approval.

Right-of-way: RPAS give way to all manned aircraft; never assume the manned pilot sees you. See-and-avoid is the remote pilot's responsibility.

Temporary restrictions: NOTAMs, airspace closures, and event-based TFRs (e.g., VIP movement, disaster response) override normal limits; check NOTAMs before every flight.

Night operations require anti-collision lighting visible for the prescribed distance and prior approval; operations in cloud or reduced visibility are normally prohibited under VFR see-and-avoid.

Site survey checklist: launch/recovery area size and surface, obstructions and their heights, overhead wires, terrain slope, bystander access, and emergency landing zones.

Airspace check sequence: NOTAMs, controlled airspace boundaries, aerodrome proximity, restricted/prohibited areas, and required ATC or CAAP approval status confirmed before departure.

Weather go/no-go: check surface wind (gust spread), visibility, cloud base versus planned altitude, precipitation, and lightning within the operating area; define hard limits in the operations manual.

Crew and role brief: remote pilot in command, visual observer, and any payload operator; confirm communication method, lost-link actions, and abort criteria before arming.

Pre-flight inspection: airframe cracks, motor mounts, propeller condition, battery state of charge and swelling, wiring and connectors, gimbal, landing gear, and firmware/software status.

Control link and payload check: confirm telemetry, video, and command link health, GNSS satellite count and HDOP, compass calibration, and RTH altitude setting above all obstacles.

Battery planning: reserve at least the manufacturer's low-battery and RTH reserve; compute endurance from expected hover plus transit time and derate for wind and cold.

Documentation: flight log, maintenance release, pilot certificate and currency, registration, insurance, and any approval letter carried or accessible at the site.

Multirotor control loop: flight controller fuses IMU (accelerometer/gyro), barometer, magnetometer, and GNSS to command ESCs; loss of one sensor triggers failsafe or attitude degradation.

Powerplant types: electric brushless motors with LiPo/Li-ion packs (most small RPAS); fixed-wing and larger RPAS may use reciprocating or turbine engines with fuel and ignition management.

LiPo facts: nominal 3.7 V per cell, 4.2 V full, storage ~3.8 V; never discharge below ~3.3 V per cell under load; swelling or cell imbalance means remove from service.

C-rating and capacity: max continuous current ≈ capacity (Ah) × C-rating; power draw must stay within ESC and motor ratings or overheating and shutdown follow.

Control link bands: 2.4 GHz (short range, congested), 900 MHz (longer range, better penetration), and cellular/satellite for BVLOS; antenna orientation and Fresnel zone clearance matter.

Failsafe hierarchy: signal loss → hold or continue per setting → automatic RTH at set altitude → land at home point; low battery and geofence breaches trigger separate failsafes.

GNSS limits: position hold depends on satellite count and HDOP; multipath near buildings and trees degrades accuracy; loss of GNSS drops the aircraft to attitude mode.

Redundancy: dual IMU, dual compass, redundant power rails, and dual control links exist on larger RPAS; know which failures are survivable and which force an immediate landing.

Wind gradient: surface friction reduces wind near the ground; wind speed increases with height, and direction veers with altitude in the Northern Hemisphere, so low-level wind differs from forecast winds aloft.

Gust spread = peak gust minus mean wind; large spread signals turbulence and requires added control margin and reduced maximum operating wind.

Density altitude rises with high temperature, high elevation, and high humidity, reducing lift and propeller/engine performance; plan shorter endurance on hot afternoons.

Convective hazards: cumulonimbus implies strong updrafts/downdrafts, hail, lightning, and microbursts; keep a wide lateral buffer and land before the storm arrives.

Visibility and cloud: VFR see-and-avoid requires cloud clearance and visibility; fog and low stratus form near dawn with light wind and high humidity.

Local effects: sea breezes (afternoon onshore flow), valley/mountain winds, urban heat island updrafts, and rotor turbulence downwind of buildings and ridges.

METAR/TAF decode: wind direction/speed/gust, visibility, cloud layers and bases, temperature/dewpoint spread, QNH; a small temperature-dewpoint spread predicts fog or low cloud.

Icing and precipitation: even light icing degrades small propellers and airframes; rain increases weight and can ingress electronics; avoid flight in freezing precipitation.

Coordinate formats: WGS84 latitude/longitude in decimal degrees or degrees-minutes-seconds; always state the datum (WGS84) and format to avoid misplacement.

Position reporting elements: identification, position (coordinates or bearing/distance from a known point), altitude (AGL and/or AMSL), time, and intentions.

Map reading: identify grid north versus magnetic north (declination in the Philippines is small but nonzero), scale, contour interval, and obstacle/obstruction markings.

Altitude references: AGL for regulatory limits, AMSL for terrain clearance and airspace; convert using local elevation and keep RTH altitude above the highest obstacle plus margin.

Geofencing: define polygons for the operating area and no-go zones; verify fence limits in the control station before flight and confirm behavior at the boundary.

Route planning: build waypoints with altitude, speed, and hold time; check terrain profile and obstacle clearance along each leg, not just at waypoints.

Lost orientation recovery: use the map/attitude indicator, home direction arrow, and telemetry heading; if disoriented, stop, gain altitude if safe, and navigate by map.

GNSS accuracy: HDOP/VDOP and satellite geometry affect position error; do not rely on a single fix for precision work without an RTK/PPK correction source.

Standard phraseology: use ICAO spelling alphabet, digits pronounced individually, and standard words (ROGER, WILCO, STANDBY, SAY AGAIN, CORRECT, NEGATIVE).

Call structure: station called, own station, position, altitude, and request; keep transmissions brief and read back clearances, altitudes, and frequencies.

Frequency discipline: monitor the assigned frequency, use the correct aeronautical band for ATC, and never transmit on guard or emergency frequencies except in emergency.

Readback items: ATC clearances, runway/area assignments, altitude restrictions, and frequency changes must be read back verbatim.

Lost communication: squawk/announce per procedure, attempt contact on the last assigned and standby frequencies, then follow the pre-briefed lost-comms plan and land.

Emergency call: MAYDAY (distress, three times) with callsign, position, altitude, nature of problem, and intentions; PAN-PAN for urgency without immediate danger.

Crew communications: use clear, closed-loop callouts between remote pilot and observer (e.g., 'clear to launch', 'traffic at 2 o'clock, high'); confirm each instruction.

Radio checks and interference: verify battery, antenna, and volume before flight; if interference or blocked frequency, switch to the agreed backup channel.

Threat and error management: identify threats (weather, terrain, traffic) before flight, trap errors with briefings and checklists, and manage undetected errors after they occur.

Situational awareness: maintain the picture from telemetry, visual observation, and radio; degradation signs include fixation on the screen, channelized attention, and ambiguity.

Fatigue and circadian effects: vigilance drops with long duty days and early starts; set maximum duty and rest limits in the operations manual and enforce them.

Automation bias: over-trust in RTH and autopilot can mask failures; monitor raw telemetry and be ready to take manual control.

Crew coordination: define roles (pilot flying, pilot monitoring, observer), use closed-loop communication, and flatten authority so any crew member can call an abort.

Decision-making models: use FORDEC or similar (facts, options, risks, decision, execute, check) for time-available decisions; use pre-briefed go/no-go criteria for time-critical ones.

Stress and workload: high workload narrows attention; offload by delegating observation and checklist reading, and brief the abort/land criteria before launch.

Just culture and reporting: report errors and near misses without blame so hazards are captured; use occurrence reports to update procedures.

Lost link sequence: verify antenna/connection, allow the aircraft to execute its programmed failsafe (hold, RTH, or land), and clear the area; do not chase the aircraft.

RTH parameters: set RTH altitude above all obstacles along the return path, confirm home point is correct before flight, and know the behavior if GNSS is lost during RTH.

Emergency landing priorities: people first, then property, then the aircraft; choose the nearest clear area away from bystanders and announce the descent.

Battery emergency: land immediately at the low-battery warning threshold; never extend to the critical threshold, which triggers forced auto-land.

Fly-away: activate the independent termination system if fitted, notify ATC/authority, log the last known position and time, and do not attempt to intercept with another aircraft.

Fire response (LiPo): isolate the pack, use a Class D or appropriate lithium fire agent or copious water, avoid inhaling fumes, and evacuate if the fire spreads.

Injury and accident: render aid, secure the site, notify CAAP within the required time, preserve data and wreckage, and file the occurrence report.

Post-incident: download logs, preserve evidence, conduct a non-punitive review, and correct procedures or maintenance before resuming operations.

Operator responsibilities: hold the required certificate, maintain an operations manual accepted by CAAP, and ensure every flight is within the certificate's scope and limitations.

Pilot responsibilities: hold a valid remote pilot certificate, meet medical and currency requirements, and act as final authority for the safety of the flight.

Flight authorization: obtain ATC clearance for controlled airspace and CAAP approval for BVLOS, night, over-people, or above-limit operations before launch.

Record keeping: retain flight, maintenance, training, and incident records for the period specified in Part 10.5 and make them available on request.

Insurance and liability: commercial operations generally require third-party liability cover; confirm the policy covers the aircraft, payload, and operating area.

Privacy and data: comply with the Data Privacy Act when capturing images or data over private property; obtain consent where required.

Environmental and noise: avoid unnecessary noise over residential areas and respect local government ordinances in addition to CAAP rules.

Reporting: notify CAAP of accidents, serious incidents, and changes to the operator's organization or fleet within the prescribed timeframes.

Maintenance program: follow the manufacturer's schedule plus any CAAP-accepted operator requirements; record every inspection, repair, and component change.

Battery management: log charge cycles, storage voltage, internal resistance, and swelling; retire packs at the manufacturer's cycle limit or on any abnormality.

Propeller and motor checks: inspect for cracks, nicks, and imbalance; verify motor temperature, bearing play, and secure mounts after each flight.

Firmware and software control: track versions, test updates on the ground before flight, and keep a rollback plan; unverified updates are a maintenance action.

Structural inspection: check airframe, arms, landing gear, and payload mounts for cracks and loose fasteners, especially after hard landings.

Return-to-service: after any incident or hard landing, complete a documented inspection and functional test before the next flight.

Spare parts and configuration: use manufacturer-approved parts; document configuration changes that affect weight, balance, or performance.

Calibration: perform compass and IMU calibration when prompted or after significant changes; verify sensor health on the ground before flight.

Payload types: RGB, thermal, multispectral, LiDAR, and spray systems; each changes weight, balance, endurance, and the required approvals.

Data link budget: range depends on transmit power, antenna gain, frequency, and terrain; keep line of sight and clear the Fresnel zone for reliable video and telemetry.

Frequency coordination: 2.4 GHz and 5.8 GHz are shared with Wi-Fi; 900 MHz penetrates better but is congested in urban areas; choose channels to avoid interference.

Video latency: high latency degrades manual control and observer coordination; test latency on the ground and set a maximum acceptable value.

Payload security: encrypt or protect data links where required; secure storage and transfer of imagery under the Data Privacy Act.

Spray and dispensing: follow label rates, buffer zones, wind limits, and record application data; avoid drift onto bystanders and water bodies.

Sensor calibration: radiometric and geometric calibration for multispectral and LiDAR payloads; record calibration files with the mission data.

Mission planning software: verify geofence, waypoint altitudes, and failsafe settings in the software and on the aircraft before launch.

Controlled aerodrome: contact ATC before flight within the control zone; provide position, altitude, duration, and area of operation, and comply with instructions.

Aerodrome traffic: RPAS normally operate outside approach and departure paths; coordinate with the tower and aerodrome operator for any operation inside the traffic area.

NOTAM and AIP: check NOTAMs for closures, obstacles, and temporary restrictions; use AIP charts to identify controlled airspace and aerodrome boundaries.

Transponder and surveillance: where required, operate a transponder or electronic conspicuity device per ATC instruction; otherwise remain clear of controlled airspace.

Emergency coordination: declare MAYDAY/PAN-PAN to ATC, state position and intentions, and follow instructions; ATC can separate manned traffic from the area.

Communication failure: follow the pre-briefed lost-comms procedure, remain clear of traffic, and land as soon as safe.

Airshow and event operations: obtain special approval and coordinate with the event organizer and ATC; temporary restrictions apply.

Military and security areas: coordinate with the controlling authority; unauthorized entry can trigger interception and enforcement action.

Risk matrix: likelihood × severity; define acceptable, tolerable, and unacceptable levels in the operations manual and apply them to every flight.

SORA-style thinking: identify ground and air risk, apply containment and mitigation, and document the residual risk and its acceptance.

Hazard identification: use checklists, site surveys, occurrence reports, and near-miss data to find hazards before they cause harm.

Mitigation hierarchy: eliminate, substitute, engineer controls, administrative controls, then PPE; prefer engineering controls over procedure alone.

Safety performance: track leading indicators (checklist completion, currency, maintenance on time) and lagging indicators (incidents, near misses, violations).

Change management: reassess risk when the site, aircraft, payload, crew, or procedure changes; do not assume prior approval covers new conditions.

Safety culture: encourage reporting, learn from errors, and review procedures after every incident or significant near miss.

Documentation: keep risk assessments, approvals, and briefings with the flight record for audit and continuous improvement.

Rule currency: CAAP RPAS rules evolve; check the CAAP website and PCAR Part 10.5 amendments before relying on older guidance.

Pilot currency: maintain recency and proficiency requirements; complete recurrent training and assessment within the period set by CAAP.

Training records: document initial and recurrent training, assessments, and flight hours; produce them on request.

Operations manual: keep it current with the actual fleet, procedures, and approvals; CAAP acceptance is tied to the documented version.

Technology change: new aircraft, payloads, and software require updated risk assessment and, where applicable, CAAP approval.

International operations: foreign operations require the host state's permission and may require additional certification; do not assume Philippine approval is sufficient.

Incident learning: review CAAP safety notices and occurrence reports to update procedures and training.

Professional development: track regulatory changes, attend briefings, and maintain a personal log of training and experience.

Privacy: comply with the Data Privacy Act when capturing images or data over private property; obtain consent where required and secure the data.

Honesty: report accidents, incidents, and violations accurately and promptly; falsifying records is a serious violation.

Respect for others: avoid noise and nuisance over residential areas and respect local ordinances.

Conflict of interest: disclose relationships that could compromise safety decisions.

Professional competence: fly within your training and currency; decline missions beyond your capability or approval.

Environmental responsibility: minimize disturbance to wildlife and sensitive areas; follow environmental regulations.

Public safety: prioritize people and property over the aircraft in any emergency.

Continuous improvement: learn from errors and share lessons without blame.

Role clarity: define pilot flying, pilot monitoring, and observer duties before flight; confirm who calls abort and who handles radio.

Closed-loop communication: sender states the message, receiver repeats it back, sender confirms; use it for every clearance and instruction.

Briefing: cover threats, weather, airspace, emergency actions, and abort criteria; confirm understanding with questions, not yes/no.

Workload management: distribute tasks, use checklists, and call 'unable' when task saturation threatens safety.

Situational awareness: cross-monitor telemetry and visual observation; challenge deviations early and speak up.

Decision-making: use time-available models for complex choices and pre-briefed criteria for time-critical ones.

Fatigue and stress: set duty limits, rotate roles, and take breaks; fatigue degrades judgment before it is noticed.

Debrief: review what went well and what to change; feed lessons into procedures and training.

Immediate priorities: protect people, secure the site, and prevent fire or further harm.

Notification: notify CAAP and, where applicable, ATC and local authorities within the required timeframe.

Evidence preservation: do not move wreckage or data unless needed for safety; photograph and record the scene.

Data recovery: download flight logs and preserve them; they are key to understanding the event.

Witness statements: record names and contact details and statements while memory is fresh.

Investigation cooperation: cooperate fully with CAAP and other authorities; do not obstruct.

Corrective action: identify root causes, update procedures and training, and verify effectiveness before resuming.

Reporting culture: share lessons without blame to prevent recurrence.

Pre-flight airspace check: confirm class, restrictions, NOTAMs, and approvals for the exact operating area and altitude.

Boundary discipline: stay inside the approved area and below the approved altitude; geofences are a backstop, not a substitute for judgment.

Clearance compliance: follow ATC instructions exactly; if unable, say 'unable' and state the reason.

Record keeping: keep approvals, flight logs, and risk assessments with the flight record.

Change control: re-check airspace and approvals when the site, time, or altitude changes.

Incident reporting: report airspace violations and near misses promptly.

Currency: verify pilot and aircraft currency before flight.

Professional judgment: decline flights that cannot be conducted safely within the rules.

Position format: state latitude/longitude in WGS84 with the format used (decimal or DMS); include bearing/distance from a known point when useful.

Altitude reporting: state AGL and AMSL clearly; confirm the reference used.

Time: use UTC or local time consistently and state which.

Intentions: state what you plan to do (hold, transit, land) and the expected duration.

Map use: identify obstacles, terrain, and airspace boundaries before flight; verify with the chart and the control station.

Lost orientation: stop, gain altitude if safe, and navigate by map and telemetry.

GNSS accuracy: note HDOP and satellite count; do not rely on a single fix for precision work.

Communication: use standard phraseology and read back clearances.

Wind: check surface wind and gusts; set a maximum operating wind and gust spread.

Density altitude: high temperature, elevation, and humidity reduce performance; derate endurance.

Convection: avoid cumulonimbus and lightning; land before the storm.

Visibility and cloud: maintain VFR cloud clearance and visibility.

Local effects: sea breezes, valley winds, and urban turbulence.

METAR/TAF: decode wind, visibility, cloud, temperature/dewpoint, and QNH.

Icing and precipitation: avoid freezing precipitation and heavy rain.

Go/no-go: apply pre-briefed weather limits.

Control loop: IMU, barometer, magnetometer, and GNSS feed the flight controller; know the failure modes.

Power: LiPo voltage limits and C-rating; monitor battery state.

Control link: frequency choice, antenna orientation, and Fresnel zone.

Failsafe: know the RTH altitude and behavior on link loss.

GNSS: satellite count and HDOP; multipath near buildings.

Redundancy: know which failures are survivable.

Pre-flight: check sensors, firmware, and calibration.

Emergency: take manual control when automation misbehaves.

Site survey: launch/recovery area, obstructions, bystanders, and emergency landing zones.

Airspace: NOTAMs, class, restrictions, and approvals.

Weather: wind, visibility, cloud, and precipitation limits.

Crew brief: roles, communications, and abort criteria.

Pre-flight inspection: airframe, propellers, batteries, and firmware.

Link and payload: telemetry, video, GNSS, and RTH altitude.

Battery planning: reserve and derate for wind and cold.

Documentation: logs, certificates, and approvals.

Operator certificate: confirm scope and limitations.

Pilot certificate: valid, current, and medically fit.

Approvals: ATC clearance and CAAP approval where required.

Records: flight, maintenance, training, and incident logs.

Insurance: third-party liability for commercial operations.

Privacy: Data Privacy Act compliance.

Noise and environment: local ordinances and wildlife.

Reporting: accidents and serious incidents within the required time.

Risk matrix: likelihood × severity.

Hazard identification: checklists, surveys, and occurrence reports.

Mitigation hierarchy: eliminate, substitute, engineer, administrate, PPE.

Safety performance: leading and lagging indicators.

Change management: reassess when anything changes.

Safety culture: reporting and learning.

Documentation: risk assessments and briefings.

Continuous improvement: review and update procedures.

Threat and error management: identify, trap, and manage.

Situational awareness: cross-monitor and speak up.

Fatigue: duty limits and rest.

Automation bias: monitor raw data.

Crew coordination: roles and closed-loop communication.

Decision-making: FORDEC for time-available decisions.

Stress: offload and delegate.

Just culture: report without blame.

Lost link: verify, allow failsafe, clear the area.

RTH: altitude above obstacles and correct home point.

Landing priorities: people, property, aircraft.

Battery: land at the low-battery warning.

Fly-away: termination system, notify, log.

LiPo fire: isolate, use appropriate agent, evacuate.

Injury: aid, secure, notify, preserve data.

Post-incident: download logs, review, correct.

Phraseology: ICAO alphabet and standard words.

Call structure: station, own station, position, altitude, request.

Readback: clearances, altitudes, and frequencies.

Lost communication: follow the pre-briefed plan.

Emergency: MAYDAY/PAN-PAN with position and intentions.

Crew calls: closed-loop and confirm.

Radio check: battery, antenna, and volume.

Interference: switch to the backup channel.

Default limits: 400 ft AGL and VLOS.

Controlled airspace: ATC coordination.

Prohibited areas: aerodromes, military, and security zones.

Buffers: aerodrome traffic zone and approach paths.

Distance from people: prescribed lateral distance.

Right-of-way: give way to manned aircraft.

Temporary restrictions: NOTAMs and TFRs.

Night: lighting and approval.

Coordinates: WGS84 and format.

Position report: identification, position, altitude, time, intentions.

Maps: declination, scale, contours, and obstacles.

Altitude: AGL vs AMSL and RTH margin.

Geofence: define and verify.

Route: waypoints and obstacle clearance.

Lost orientation: stop, climb, navigate by map.

GNSS: HDOP and satellite geometry.

Wind gradient: wind increases with height.

Gust spread: turbulence indicator.

Density altitude: temperature, elevation, and humidity.

Convection: avoid cumulonimbus.

Visibility and cloud: VFR minima.

Local effects: sea breeze and urban turbulence.

METAR/TAF: decode and apply.

Icing: avoid freezing precipitation.

Rule currency: check CAAP amendments.

Pilot currency: recurrent training and assessment.

Training records: document and produce on request.

Operations manual: keep current.

Technology change: reassess and approve.

International: host state permission.

Incident learning: review safety notices.

Professional development: track changes and log experience.