Spend $90 more for free shipping
Drone GuidesPractical learning route
A CAAM-led checklist for Malaysia drone operations: Authorisation to Fly, operation category, remote-pilot competency, site planning and current approval checks.
Updated September 7, 2026. In Malaysia, a small drone’s weight is not a complete answer to whether a flight can proceed. The Civil Aviation Authority of Malaysia (CAAM) states in its 2025 Authorisation to Fly guidance that a person intending to operate an Unmanned Aircraft System must obtain prior authorisation from CAAM. The appropriate pathway depends on the operation, the risk, the airspace, the aircraft, and the activity planned.
This English guide is a planning aid, not a permit. It does not approve a recreational launch, a business shoot, an FPV event, an imported product, or a specific location. Check the current CAAM application material before each operation, because the proposed flight details determine the approval path.
A sub-250 g aircraft may be physically small, but that label does not replace CAAM authorisation. Record the exact model, take-off mass, intended location, altitude, date, time, visual-line-of-sight plan, and purpose of the flight. A rooftop inspection, a hotel marketing video, a club race, a farm survey, and a short recreational flight can create different operational questions even when the same aircraft is used.
CAAM’s current Safety Information 01/2025 identifies a low-risk pathway for operations conducted within visual line of sight, below 400 ft AGL, and excluding spraying or dispensing: the operator and/or remote pilot acquires an Authorisation to Fly (ATF). This is an authorisation workflow, not a blanket outcome for every light aircraft. A proposed flight must still be assessed against the information and conditions CAAM requires.
Read CAAM Safety Information 01/2025 and use the current CAAM UAS application page before setting a date or promising a client a flight.
CAAM publishes more than one UAS route. A Standard ATF is relevant to the lower-risk conditions CAAM describes. Agricultural UAS operations have their own Unmanned Aerial Work Certificate pathway. CAAM describes a Special UAS Project as an operation involving dangerous goods, beyond visual line of sight, research and development, or other activities that require additional operational support because of the risk involved.
This is why an operator should not relabel an operation to fit a preferred answer. Adding a dangerous-goods payload, extending a route beyond visual line of sight, or changing a routine visual flight into a development test can move the project into a different approval context. Where the project does not clearly fit the low-risk conditions, stop and seek the current CAAM direction before flying.
CAAM’s UAS guidance describes Standard ATF, agricultural UAS operations, and Special UAS Project approval in one place.
CAAM’s published guidance distinguishes operational authorisation from the remote-pilot competency routes it describes. On its UAS page, CAAM explains the Remote Pilot Certificate of Competency (RCoC-B) and relevant modules in the Special UAS Project and agricultural contexts. It also notes that an RCoC-B is not automatically required for a Standard ATF application merely because the activity involves mapping or surveillance within the stated visual-line-of-sight context.
That does not mean competence becomes optional. It means the operator should read the requirement that belongs to the proposed operation rather than repeating a generic “license required” or “license not required” claim. Keep the named remote pilot, observer if any, operator, and project manager clear in the application and in the day-of-flight record. CAAM’s UAS guidance says people involved in the operation, including remote pilot, observer, and project manager, must be identified.
Location changes the decision. A controlled-airspace question, a restricted site, an event with spectators, an emergency response, a property manager’s conditions, and a road or construction area should be considered before equipment is unpacked. Use the precise launch and recovery point, intended route, height, and time. Do not treat an old no-fly map, a geo-fence prompt, or a social-media post as CAAM approval.
For an event or filming project, agree with the organiser and landowner where the aircraft can be launched and recovered, who will manage access, and who can stop the operation. A safe plan has an abort route and a clear cancellation threshold for weather, people, airspace, radio link, or aircraft condition. CAAM’s UAS material calls for current conditions and risk to be considered; the operator should never let a production timetable substitute for that check.
Build the application record so another responsible person can understand the decision without relying on memory. Keep the model identification, intended operating area, planned height, dates, people involved, and the submitted approval route together. Before launch, compare that plan with the aircraft actually being used and the conditions at the site. A changed location, route, aircraft, operating team, or activity can be material; do not assume that a prior approval automatically describes a revised operation.
For a client-facing project, avoid marketing language such as “CAAM approved” unless the statement identifies the specific approved operation and remains accurate at the time it is published. The practical question is not whether a drone brand is generally capable of flying in Malaysia. It is whether this operation, at this place and time, is within the current authorisation and safety plan.
A flight authorisation guide cannot certify that an imported drone, controller, or battery has cleared customs or satisfies every radio, product, carrier, or tax requirement. Those questions can involve agencies and evidence outside CAAM’s flight-operation materials. Do not interpret an ATF or other CAAM approval as a customs clearance, a radio approval, or a carrier acceptance. Obtain the current decision from the authority responsible for each separate issue.
