Manufacturer vs Flight Module Provider


There is a bit of confusion between the roles of Manufacturer vs Flight Module Provider as per NPNT.

On Page 32 of RPAS Guidance Manual, Section 1.3:

In this document, the term “Flight Module Provider” is used to refer to a RPAS manufacturer or any agency who has partnership with the manufacturer to manage certification and related software/security aspects of registered flight modules

This implies that Flight Module Provider can be a different entity from Manufacturer. In such a case, the Flight Module Provider will be primarily responsible for key management. In Digital Sky, the Manufacturer is required to upload a Trusted Certificate Chain. This implies that the Manufacturer and the Flight Module Provider are considered as one.

One way to fix this could be to have Flight Module Provider as a separate entity and have separate roles for Flight Module Provider and Manufacturer.

  • Manufacturer: Responsible for submitting RPAS list application with all the required documents
  • Flight Module Provider: Responsible for uploading the Trusted Certificate Chain and key management

Your thoughts?

@sid @sidbh @sidhant


Hi Abhiroop,

The manufacturer is responsible for safety and identification of their drones and the policies implemented which is the source of the drone for DS platform. The manufacturer may have a partnership with an agency providing key management and other security that means the manufacturer is already trusting RFM provider.


Inferring from the above discussion there must be a module which handles certification and permission before takeoff in flight?


For permission, it’s called the RFM Module. Please see Chapter 7 for its specification:

Certification covers more than the RFM module - it includes many other aspects of Air Worthiness. Please see Chapter 6 and Chapter 8 for details on the same.


Hello guys…
I have a big confutions with key pairs RFM public and private keys.
My very first thinking was those key pairs are provided by digital sky.
But those keys need to genarated in RFM itself.
*So how I will genrate private and publick keys - from X509 certificate comes with PA or by using openssl functions.
*After genarting will I need to sign it with dsc token or somthing else?

Please help me,