Nigeria - CARS-Part-21
Nigeria - CARS-Part-21
Nigeria - CARS-Part-21
REGULATIONS
PART 21
REMOTELY PILOTED AIRCRAFT SYSTEMS (RPAS)
2023
NIGERIA CIVIL AVIATION
REGULATIONS Part 21 –Remotely Piloted Aircraft Systems
(RPAS) Regulations
APRIL 2023
ii
NIGERIA CIVIL AVIATION Part 21 –Remotely Piloted Aircraft Systems
REGULATIONS (RPAS) Regulations
Record of Amendment
iii
NIGERIA CIVIL AVIATION Part 21 –Remotely Piloted Aircraft Systems
REGULATIONS (RPAS) Regulations
PART 21
REMOTELY PILOTED AIRCRAFT SYSTEMS (RPAS)
APRIL 2023
iv
NIGERIA CIVIL AVIATION Part 21 –Remotely Piloted Aircraft Systems
REGULATIONS (RPAS) Regulations
CONTENTS
v
NIGERIA CIVIL AVIATION Part 21 –Remotely Piloted Aircraft Systems
REGULATIONS (RPAS) Regulations
vi
NIGERIA CIVIL AVIATION Part 21 –Remotely Piloted Aircraft Systems
REGULATIONS (RPAS) Regulations
vii
NIGERIA CIVIL AVIATION Part 21 –Remotely Piloted Aircraft Systems
REGULATIONS (RPAS) Regulations
21.13.1.3 Physical Security of the Installed RPS When not In Use …………..…………21-60
21.13.1.4 Physical Security of Mobile RPS …………………………………………...……21-60
21.13.1.5 Command and Control (C2) Link Security …………………………………...…21-60
21.13.1.6 Security Management of RPAS ………………………………………….………21-61
21.13.1.7 Emergency / Contingency Plan …………………………………….……………21-62
21.13.1.8 Aerodrome Operations ……………………………………………………………21-62
21.14 REQUIREMENTS FOR MANUFACTURER ……………………………………………21-62
21.14.1.1 Applicability ………………………………………………………………………..21-62
21.14.1.2 Means of Compliance …………………………………………………….………21-63
21.14.1.3 Manufacturer Declaration …………………………………………...……………21-63
21.14.1.4 Notice to the Authority ………………………………………….…………………21-64
21.14.1.5 Documentation ……………………………………………………….……………21-64
21.14.1.6 Record Retention for Manufacturer ……………………………………..………21-65
21.15 TRANSPORT OF DANGEROUS GOODS ON RPAS ……………………………...…21-65
21.15. 1.1 General Principles ……………………………………………………………...…21-65
21.16 CARGO COMPARTMENT SAFETY …………………………………….………………21-67
21.16.1.1 Transport of Items in the Cargo Compartment …………………………...……21-67
2.16.1.2 Fire Protection ……………………………………………………………………..21-67
21.17 GENERAL PROVISIONS ……………………………………………………….………..21-68
21.17.1.1 Insurance …………………………………………………………….…….………21-68
21.18.1.1 Privacy of Persons and Property ……………………………………….….……21-68
21.18.1.2 Discharging or Dropping Goods …………………………………………………21-68
21.18.1.3 Reports of Violation ………………………………………………..……………..21-69
RPAS REGULATIONS IMPLEMENTING STANDARDS (IS) ……………………..…………21-70
IS: 21.5.2.1 APPLICATION FOR ISSUE / RENEWAL / VARIATION OF REMOTELY
Piloted Aircraft (RPA) ……………………………………………………………..21-71
IS 21.4 Certificate of Registration will be issued by the RPAS Portal in this format…21-76
IS:21.12.1.2 - (a) The C2 Link shall comply with the following performance requirements: ..21-77
IS 21.5.4 Contents of the ROC ……………………………………………………………..21-78
IS: 21.10.6.23 The operations manual shall contain at the least the following: ………..……21-83
vii
NIGERIA CIVIL AVIATION Part 21 –Remotely Piloted Aircraft Systems
REGULATIONS (RPAS) Regulations
INTRODUCTION
Part 21 sets forth the requirements for the certification, registration, operations, and
surveillance of Remotely Piloted Aircraft Systems (RPAS).
ix
NIGERIA CIVIL AVIATION Part 21 –Remotely Piloted Aircraft Systems
REGULATIONS (RPAS) Regulations
21.1 GENERAL
21.1.1 Applicability
(a) a control-line model aircraft (that is, a model aircraft that is constrained to
fly in a circle, and is controlled in attitude and altitude, by means of
inextensible wires attached to a handle held by the person operating the
model); or
(d) a small balloon within 100 metres of a structure and not above the top of
the structure; the operation of a remotely piloted balloon or a hot air
balloon, or
(e) remotely piloted tethered balloon that remains below 400 feet above
ground level; or
(f) a firework rocket not capable of rising more than 400 feet above ground
level.
21.1.1.3 A flight does not take place indoors in accordance with 21.1.1.2 of this
regulations, if the building in which it takes place has the roof, or one (1) or
more walls, removed.
21.1.1.4 All RPAS classified under subsection 21.2.1.2 shall be registered by the
Nigeria Civil Aviation Authority.
(i) the flights are below Four Hundred feet (400 ft) AGL ;
(iv) the flights are not conducted over any congested area;
(v) the RPAS is in compliance with all relevant sections of this Part and
any regulations and laws of the Federal Republic of Nigeria;.
21.1.2 Definitions
— direct contact with any part of the aircraft, including parts which have
become detached from the aircraft, or
— direct exposure to jet blast, except when the injuries are from natural
causes, self-inflicted or inflicted by other persons, or when the injuries are
to stowaways hiding outside the areas normally available to the
passengers and crew; or
Note 1.— For statistical uniformity only, an injury resulting in death within
thirty days of the date of the accident is classified, by ICAO, as a fatal
injury.
Aircraft means any machine that can derive support in the atmosphere
from the reactions of the air other than the reactions of the air against the
earth’s surface.
Air traffic control service. A service provided for the purpose of:
a) preventing collisions:
i. between aircraft, and
Air traffic control unit means a generic term meaning variously, area
control centre, approach control unit or aerodrome control tower.
Air traffic services unit means a ge neric term meaning variously, air
traffic control unit, flight information centre or air traffic services reporting
office.
Note 1.— The aircraft operating manual is part of the operations manual.
Note 2.— For RPAS, this includes information related to the whole system,
including the RPS.
Note.— The aerodrome from which a flight departs may also be an en-
route or a destination alternate aerodrome for that flight.
C2 Link means the data link between the remotely piloted aircraft and the
remote pilot station for the purposes of managing the flight.
C2 Link coverage area means the area in which the C2 Link service can
be received including the area where the QoSD does not meet the QoSR.
C2 Link service area means the area within the C2 Link coverage area
where the C2 Link QoSD meets the QoSR.
Defined point after take-off (DPATO) means the point, within the take -
off and initial climb phase, before which the helicopter’s ability to continue
the flight safely, with one engine inoperative, is not assured and a forced
landing may be required.
Defined point before landing (DPBL) means the point, within the
approach and landing phase, after which the helicopter’s ability to continue
the flight safely, with one engine inoperative, is not assured and a forced
landing may be required.
Detect and avoid means the capability to see, sense or detect conflicting
traffic or other hazards and take the appropriate action.
Duty means any task that flight or cabin crew members are required by
the operator to perform, including, for example, flight duty, administrative
work, training, positioning and standby when it is likely to induce fatigue.
Duty period means a period which starts when a flight or cabin crew
member is required by an operator to report for or to commence a duty and
ends when that person is free from all duties.
Note.— For RPAS this includes remote flight crew members and other
remote crew members.
Educational Research RPAS operations generally denotes RPAS used
to perform scientific studies, such as weather research or geophysical
surveying.
Note.— For RPAS, this includes information related to the whole system,
including the RPS and remote flight crew members.
Flight simulation training device means any one of the following three
types of apparatus in which flight conditions are simulated on the ground:
Note.— For RPAS, the RPS is equivalent to the “flight deck,” and may not
be specific to the type of RPA being used.
Flight time – remotely piloted aircraft systems means the total time
from the moment a C2 Link is established between the remote pilot station
(RPS) and the remotely piloted aircraft (RPA) for the purpose of taking off
or from the moment the remote pilot receives control following a handover
until the moment the remote pilot completes handover or the C2 Link
between the RPS and RPA is terminated at the end of the flight.
Handover means the act of passing piloting control from one remote pilot
station to another.
IFR means the symbol used to designate the instrument flight rules.
Landing area means that part of a movement area intended for the
landing or take- off of aircraft.
Lost C2 Link decision state means the state of the RPAS in which a C2
Link interruption has occurred, but the duration of which does not exceed
the lost C2 Link decision time.
Lost C2 Link state means the state of the RPAS in which the C2 Link
performance has degraded, as a result of a C2 Link interruption that is
longer than the lost C2 Link decision time, to a point where it is not
sufficient to allow the remote pilot to actively manage the flight in a safe
and timely manner.
Minimum equipment list (MEL) means a list which provides for the
operation of aircraft, subject to specified conditions, with particular
equipment inoperative, prepared by an operator in conformity with, or more
restrictive than, the MMEL established for the aircraft type.
Note.— For RPAS this includes inoperative equipment of the RPAS, not
only the RPA.
Nominal C2 Link state means the state of the RPAS when the C2 Link
performance is sufficient to allow the remote pilot to actively manage the
flight of the RPA in a safe and timely manner appropriate to the airspace
and operational conditions.
Note.— For RPAS these specifications are associated with the RPAS
operator certificate.
Note.— For RPAS this includes all parts and components of the RPAS, not
only the RPA.
Permit means a generic term for any approval to fly an RPAS granted by
the Authority.
in the order of priority, with preferred performance value for each criterion.
The C2CSP then translates these into parameters and metrics pertinent to
the service.
Remote cruise relief pilot means a remote flight crew member who is
assigned to perform remote pilot tasks during cruise flight, to allow the
remote pilot-in- command to obtain planned rest.
Note.— For RPAS, this applies to remote flight crew members and other
remote crew members.
Safety means the state in which risks associated with aviation activities,
related to, or in direct support of the operation of aircraft, are reduced and
controlled to an acceptable level.
Note 1.— The difference between an accident and a serious incident lies
only in the result.
State of Design means the State having jurisdiction over the organization
responsible for the type design.
Note 2.— For RPAS, this refers to the State on whose register the RPA is
entered.
State of the Operator means the State in which the operator’s principal
place of business is located or, if there is no such place of business, the
operator’s permanent residence.
State of the RPS service provider. means the State where the RPS
service provider has its primary place of business.
Switchover means the act of transferring the active data link path
between the RPS and the RPA from one of the links or networks that
constitutes the C2 Link to another link or network that constitutes the C2
Link.
Target level of safety (TLS) means a generic term representing the level
of risk which is considered acceptable in particular circumstances.
VFR means the symbol used to designate the visual flight rules.
VFR flight means a flight conducted in accordance with the visual flight
rules.
Switchover means the act of transferring the active data link path
between the RPS and the RPA from one of the links or networks that
constitutes the C2 Link to another link or network that constitutes the C2
Link.
(a) The following abbreviations and acronyms are used in this Part.
21.1.4 Exemptions
(a) Exemptions under this Part are granted in accordance with Part 1 of these
Regulations.
(i) Small: Greater than 250g but less than or equal to 25kg and shall
be flown only within the visual line of sight of the pilot with prior
authorisation of the Authority.
(ii) Medium: Greater than 25kg, but less than or equal to 150kg which
shall be flown either within the VLOS of the pilot or BVLOS of the pilot
with prior authorisation of the Authority.
(iii) Large: Greater than 150kg which shall be flown either within the
VLOS of the pilot or BVLOS of the pilot with prior authorisation of the
Authority.
(b) There are three (3) main operational risk categories of RPAS:
(i) Open – these present the lowest risk and do not require prior
authorisation before operating the RPAS but must be registered.
(iii) Certified – these require the RPAS and its operator and pilot to be
certified and generally treat RPAS like manned aircraft.
(b) No person may own, register or operate RPA with military specifications.
(a) No person may operate an RPAS unless the RPAS has been registered
and a certificate of registration issued by the Authority.
(c) The Authority will maintain a register of RPAS containing the information
specified in these regulations.
(e) A foreign registered RPAS shall not operate in Nigeria unless there is proof
of registration from another State or country and is authorised by the
Authority.
(a) The registration marks shall be displayed in a form and manner prescribed
by the Authority.
(a) The Authority shall remove an aircraft from the Nigerian registry if:
(1) The owner of the RPAS does not meet the eligibility provisions of
Section 21.3.1.1.
(i) The aircraft is destroyed, lost or stolen and cannot be found or;
(6) Nothing in this section shall require the Authority to cancel the
registration of an aircraft if, in its opinion, it would be inexpedient in
the public interest to do so.
No person may operate an RPA except in accordance with the terms and
conditions of the ROC.
(c) The Authority may require only those matters in paragraph (b) that the
Authority considers are appropriate in the particular circumstances to be
contained in the application.
(a) The Authority may issue an ROC to a person who has applied under
paragraph 21.4.1.2
(b) When issuing an ROC under paragraph (a), the Authority may:
(3) after considering the type of RPA to be used, determine that any
RPA to be operated under the ROC shall display identification
markings in accordance with 21.3, if the Authority considers that it is
necessary in the interest of aviation safety.
(a) The ROC shall consist of two documents – the Certificate and the
Operations Specifications in accordance with IS: 21.4.4.
(iii) the RPAS operator name, trading name (if different) and
address of the principal place of business;
(1) An ROC issued by the Authority is valid for a period of five (5) years
unless:
(b) An application for renewal of ROC shall be made at least 90 days before
the end of the existing period of validity.
(a) The PIC shall comply with the relevant laws, regulations and procedures
of the States in which the aircraft is operated.
(c) Each PIC shall submit reports specified in paragraph (b) to the Authority
within 10days in the form prescribed.
(a) The operator shall ensure that the provider of safety-critical services has
organisational structure, documented procedures, resources and
personnel sufficient to ensure the safe provision of services.
(a) The Authority will be responsible for the oversight of the C2 Link service
provision, whether any of the C2 Link components are under the control of
the RPAS operator or a C2 Link communications service provider
(C2CSP).
(b) When the operator exercises direct control over the entire C2 Link(s), the
operator shall be responsible for the safe operation of all C2 Link
components. Such responsibilities shall be detailed in a Service Level
Agreement (SLA) internal to the operator.
(c) When a portion of, or all of, the C2 Link(s) is under the operational control
of a C2CSP, the operator shall establish an SLA with the C2CSP prior to
commencing operations.
(d) The Authority will ensure that an SLA exist between the operator and
C2CSP.
(2) scope of the provided service, including hours of service and service
area;
(8) the C2CSP Emergency Response Plan (ERP) including how they
would address service losses and how they would be restored.
(g) The C2CSP shall establish and document processes to perform C2CSP
monitoring of the QoSD as part of their routine operations, with the
objective of ensuring that the C2 Link service provision meets the
applicable requirements, including the C2 Link QoSR specified in the SLA.
(h) The operator shall be responsible for monitoring that the C2 Link service
provision QoSD meets the QoSR, including its security, and shall:
(1) all C2 Link provision degradations with regards to the SLA that occur
during operations; and
(a) The operator shall be responsible for the safe operation of all RPS involved
in the operation.
(b) Each RPS used shall be installed at the intended operational location by
personnel who have the required level of expertise and competence for
the task, as determined by the type certificate holder.
(c) During installation of the RPS, the installer shall verify that it meets
applicable airworthiness and operational requirements and that it provides
proper connection with the specified RPA type(s).
(d) When one or more of the RPS involved in the operation are under the
control of a service provider, this service provider shall be under the safety
oversight of the State of the Operator in conjunction with the State of the
RPS service provider, if different.
(e) When one or more of the RPS involved in the operation are under the
control of a service provider, this service provider shall only allocate tasks
to:
(1) remote flight crews which are properly trained and competent;
(2) remote pilots holding a valid remote pilot licence (RPL) issued or
rendered valid by the State of the Operator, complemented by
appropriate ratings; and
(f) The safety, security and performance of the RPS service provided shall be
acceptable to the State of the Operator and to the State of the RPS
service provider.
(g) If the RPS is operated by an RPS service provider, the safety and security
aspects of the RPS shall be addressed in an SLA between the RPAS
operator and the RPS service provider.
(h) Any SLA with an RPS service provider shall include the continuing
airworthiness records addressed in paragraph 21.11.1.2 of this
Regulations
this purpose.
(a) No person shall operate a RPA in a manner that would cause a hazard to
persons, property or other aircraft.
(b) Operating Rules. A person operating a RPA shall comply with the general
operating rules as listed below:
(iv) not operate over the high seas without prior coordination with
the appropriate ATS Authority, which shall be obtained prior to
take-off if there is reasonable expectation, when planning the
operations, that the aircraft may enter the airspace concerned.
(vi) ensure that the RPAS meets the performance and equipment
carriage requirements for the specific airspace in which the
flight is to operate.
(2) Once authorization has been received from the Authority, the
operator shall:
(ii) notify the Authority and ATC immediately in the event of a flight
cancellation, and
(3) Remote pilots shall be licensed or have their licences rendered valid
in accordance with Nig. CARs Part 2.
(1) The request for authorisation referred to in paragraph (b) above shall
be made by providing the required information in the application form.
i) ROC;
v) MCM, maintenance log book and technical log for the RPAS;
vi) details of the filed, current, ATS and operational flight plans;
vii) current and suitable aeronautical charts for the route of flight
and all routes along which it is reasonable to expect that the
flight may be diverted, including departure, arrival and
approach charts for all relevant aerodromes or heliports;
viii) information concerning search and rescue services for the area
of the intended flight;
Note.— See Annex 4 and Annex 15, Chapter 5 and Appendix 1 and
the Procedures for Air Navigation Services — Aeronautical
Information Management (PANS-AIM), Chapter 5 for methods of
presentation of certain obstacle data.
(b) The operator shall take account of charting accuracy when assessing
compliance.
(4) notify the appropriate ATS unit when the position of the RPA cannot
be determined by an aircraft tracking capability and/or attempts to
establish communication with the remote pilot are unsuccessful.
(a) A remote pilot or person manipulating the flight controls of a RPA shall,
upon request, make available to the Authority:
(1) The remote pilot certificate; and
(2) Any other document, record, or report required to be kept under this
part.
(a) The operator shall develop procedures to ensure that a flight is not
commenced unless:
(1) the RPA is airworthy, duly registered and that appropriate certificates
with respect thereto are in possession of the RPA;
(3) the RPS(s) used for the flight is (are) serviceable and compatible with
the RPA used;
(4) a C2 link with the RPA is expected to be available for the duration of
the flight and matches the performance criteria;
(6) the mass of the RPA and centre of gravity location are such that the
flight can be conducted safely, taking into account the flight
conditions expected;
(7) any load carried is properly distributed and safely secured; and
(8) the RPA operating limitations, contained in the flight manual, or its
equivalent, will not be exceeded.
(1) the RPA is operated within the visual line-of-sight of the person
operating the RPA;
(2) the RPA is operated at or below 120m (400ft) above ground level
(AGL) by day; and
(d) the RPA is not operated over an area where a fire, police or other public
safety or emergency operation is being conducted without the approval of
a person in charge of the operation; and
(e) the person operating the RPA operates only that RPA.
(b) A RPAS operator shall not operate a RPA to which this rule applies in:
(1) any area in which the person’s view of the surrounding airspace in
which the RPA will operate is obstructed; or
(c) A person who operates a RPA to which this rule applies shall at all times:
(d) For the purposes of this rule, visual line-of-sight means a straight line along
which the remote pilot or RPA observer has a clear view and which may be
achieved with the use of:
(2) a first person view system and a trained and competent RPA
observer who maintains:
(iii) has direct communication with the person who is operating the
RPA.
(a) To conduct BVLOS operations, the operator shall obtain Authorisation from
the Authority after conducting operation safety risk assessment.
(c) Communication between the Remote Pilot Station (RPS) and the ATC
unit(s) shall be as required for the class of airspace in which operations
occur and shall utilize standard ATC communications equipment and
procedures, unless otherwise approved by the ATC unit involved.
(d) C2 link transaction time shall be minimized so as not to inhibit the remote
pilot’s ability to interface with the RPAS compared to that of a manned
aircraft.
(e) RPAS operating BVLOS shall only operate within Radio line of sight
(RLOS). Operation beyond Radio line of sight shall require special
Authorisation from the Authority after indicating all operational control
functions and safety measures associated to the type of operation.
(f) Remote Pilot Station for RPAS operations BVLOS will be designed in such
way to match the performance of the type of C2 link (BRLOS/RLOS) with
which they will be used.
(g) No person shall conduct BVLOS operations under VFR unless the
following conditions are met:
(a) Operations over heavily populated areas or over open air assemblies of
people shall require special considerations such as the following—
(3) Obstructions;
21.9.6.8 Take-off/launch
(a) For operations from established aerodromes the remote pilot shall consider
the following:
(2) at night; or
(b) 21.9.6.10 (a) does not apply if the person holds an Authorisation under this
Regulation allowing these operations.
(a) For operations from other than established aerodromes, the remote pilot
shall consider the following:
(2) location and height of all obstructions that could hinder launch and
recovery;
21.9.6.12 Landing/recovery
(a) For operations at aerodromes, the remote pilot shall consider the following:
(5) ground operations (e.g. taxiway width, condition, other ground traffic);
(a) For operations at other than aerodromes, the remote pilot shall consider
the following:
(2) location and height of all obstructions that could hinder landing or
recovery (e.g. cables, towers, trees);
(a) A person shall not operate a RPA at night unless the operation is:
(1) indoors; or
(b) 21.9.6.15 (a) does not apply if the person holds an Authorisation under
these Regulations allowing these operations.
21.9.6.17 Right-of-Way
A person who is operating a RPA shall give way to and remain clear of all
aircraft on the ground and in flight.
(a) No person shall operate a RPA over a person unless that person is:
(3) Directly associated with the operation of the RPA or the RPA is
operated no closer than 30m, measured horizontally from a second
person not directly associated with the operation of the RPA.
(1) the second person is standing behind a fixed wing RPA while the
fixed wing RPA is taking off;
(1) the person has consented that the RPA is allowed to fly over or near
a person; and
(2) the RPA is operated no closer than 15m, measured horizontally, from
a person.
(2) Unlawful Interference. The PIC shall submit a report to the local
authorities and to the Authority, without delay, following an act of
unlawful interference.
(i) notify the appropriate local Authority and NSIB without delay;
(2) Each Remote PIC shall submit reports specified in paragraph (1)
above to the Authority within 72 hours in the form prescribed by the
Authority.
(2) The period of Authorisation will be for twenty-one (21) days and
renewable based on the determination by the Authority;
(b) A request for special authorization shall be made in a form and manner as
prescribed by the Authority.
(c) The request for authorization shall be made not less than thirty days before
the date of intended operation.
(d) Copies of all pertinent certificates, the licences of the remote pilots and the
Radio Station Licence shall be included with the request for special
authorization.
(b) The programme shall address flight and duty times and be included in the
operations manual.
(c) The operator shall ensure all personnel involved in the operation and
maintenance of RPAS receive fatigue management training from an
approved organization.
(d) The operator shall ensure all personnel involved in the operation and
maintenance of RPAS do not carry out their duties while fatigued
(1) An RPAS operator must provide an operations manual for the use
and guidance of the RPAS operations personnel concerned. The
operations manual must be amended or revised as is necessary
to ensure that the information contained therein is kept up to date.
All such amendments or revisions must be issued to all personnel
that are required to use this manual.
(i) general;
(ii) RPAS operating information;
(iii) areas, routes and aerodromes; and
(iv) training.
(4) The operator shall provide the remote flight crew with an RPAS flight
manual for each RPA type operated, which includes each associated
RPS model, containing the normal, abnormal and emergency
procedures relating to the operation of all the relevant systems
associated with the operation of each RPA and of the checklists to be
used.
(a) A journey log book shall be maintained for every RPA engaged in
international air navigation in which particulars of the RPAS and its crew
shall be entered at the end of the duty period of each remote pilot-in-
command.
Note.— An RPA journey log may also consist of a section that stays in the
RPA and an RPS section at each remote pilot station.
(b) The RPA journey log shall contain the following items:
(c) A signature shall be required for each instance in which the remote pilot-in-
command is changed, which may include whilst the RPA is still airborne.
Note.— The journey log may need to accommodate multiple remote pilot-
in-command signature blocks.
(b) The format of the records shall be specified in the operator’s procedures.
(c) Records shall be stored in a manner that ensures protection from damage,
alteration and theft, for a period determined by the State of the Operator.
(1) A record containing the names of the remote pilots and other crew
members involved in each flight, in respect of the system, the time of
each flight or series of flights; and
(b) Each owner of a RPAS who transfers ownership to another person shall, at
the time of transfer, deliver to that person all records referred to in
paragraph (a)(2).
(c) Each owner of a RPAS shall ensure that the records referred to in
subsection (a)(1) and (a)(2).
(1) are made available to the Authority on request and are retained for a
period of:
21.9.6.27 Documentation
Each applicant for the issuance of an ROC shall hold copies of all
relevant equipment manuals, technical standards and practices,
technical bulletins and instructions, legislation, and any other
document that is necessary to establish procedures for their
operations.
The operator shall ensure, to the extent possible, in the event the RPAS
becomes involved in an accident or incident, the preservation of all related
RPA-RS and RPS-RS records and, if necessary, the associated recorders,
and their retention in safe custody pending their disposition as determined
in accordance with NSIB Regulations.
(a) The ROC Holder shall ensure that no flight takes place unless:
(6) the maintenance of the RPA and RPS are performed in accordance
with manufacturer data.
(b) For each RPA type, the ROC holder shall establish and implement a
maintenance programme in accordance with the manufacturer’s manuals
and considering the results of the operational risk assessment.
(c) The operator shall not operate an RPAS above 25kg unless it is
maintained and released to service by an approved maintenance
organization or Authorised person(s), either of which should be acceptable
to the Authority. The person responsible for the maintenance release shall
be licensed in accordance with Nig. CARs Part 2 of this Regulation.
(e) For each RPA and for each RPS, the operator shall maintain a Technical
Log including records of operating hours / cycles as relevant to the type of
RPA and RPS.
21.9.6.30 Airspace
(3) not operate the RPA at any height above 120m (400ft) AGL except in
accordance with paragraph (c).
(b) Nothing in paragraph (a) requires a person to obtain consent from any
person if operating:
(c) A person operating a RPA more than 4km from an aerodrome boundary
and above 120m (400ft) AGL shall ensure that the operation remains
within Class G airspace (uncontrolled airspace) and shall:
(iv) the maximum height AGL proposed for the RPA operation.
(a) Segregated. A person shall not operate a RPA within segregated airspace
unless the person has approval to do so from the administering Authority
responsible for the segregated airspace area.
(b) A person shall not operate a RPA in controlled airspace unless he or she:
(d) The Authority may direct, in regard to a particular RPA or type of RPA, that
a person must not operate the RPA, or a RPA of that type, unless the
person:
(1) holds a relevant qualification for the use of an aeronautical radio; and
(1) ensure that before each flight, the person is aware of the airspace
designation under Nig. CARs Part 14 and any applicable airspace
restrictions in place in the area of intended operation; or
(2) conduct the operation under the direct supervision of a person who is
aware of the airspace designation under Nig. CARs Part 14 and any
applicable airspace restrictions in place in the area of intended
operation.
21.9.6.36 Aerodromes
(ii) each remote pilot has a RPA observer in attendance while the
aircraft is in flight; and
(iii) the RPA is not operated at a height of more than 120 m (400 ft)
AGL unless the operator has been approved by the Authority to
operate the RPA above 120 m (400 ft) AGL; and
(i) is the holder of, or is under the direct supervision of the holder
of, a remote pilot qualification issued by an approved person or
approved aviation organization; or
(iii) is the holder of a remote pilot licence issued under Nig. CARs
Part 2 of this Regulations
(3) authorizing a person to notify the air navigation service provider, for
the issuance of a NOTAM, of a RPA operation;
Note 1.— For the purpose of this chapter, “RPA” includes: engines,
propellers, components, accessories, instruments, equipment and
apparatus including emergency equipment.
(b) The operator shall not operate an RPAS unless maintenance on the
RPAS, including any associated engine, propeller and part, is carried out:
(c) The operator shall employ a person or group of persons to ensure that all
maintenance is carried out in accordance with the maintenance control
manual.
(d) The operator shall ensure that the maintenance of its RPAS is performed
in accordance with the maintenance programme.
(e) The operator shall ensure that maintenance personnel receive initial and
continuation training acceptable to the State of the Operator that includes
the application of Human Factors principles.
(a) The operator shall ensure that the following records are kept for the
periods mentioned in 21.10.1.2(b):
(b) The records in 21.10.1.2 (a)(1) to 5) shall be kept for a minimum period of
90 days after the unit to which they refer has been permanently withdrawn
from service and the records in 21.10.1.2(a)(6) for a minimum period of
one year after the signing of the maintenance release.
(c) In the event of a temporary change of operator, the records shall be made
available to the new operator. In the event of any permanent change of
operator, the records shall be transferred to the new operator.
(d) For each RPA and for each RPS, records kept and transferred in
accordance with 21.11.1.2 shall be maintained in a form and format that
ensures readability, security and integrity of the records at all times.
Note 1.— The form and format of the records may include, for example,
paper records, film records, electronic records or any combination thereof.
(a) The operator of an RPAS approved in accordance with this Part shall
monitor and assess maintenance and operational experience with respect
to continuing airworthiness and provide the information as prescribed by
the State of Registry and report through the system specified by the
Authority.
(b) The operator of an RPAS approved in accordance with this Part shall
obtain and assess continuing airworthiness information and
recommendations available from the organization responsible for the type
design and shall implement resulting actions considered necessary in
accordance with a procedure acceptable to the State of Registry.
(a) All modifications and repairs shall comply with airworthiness requirements
acceptable to the State of Registry. Procedures shall be established to
ensure that the substantiating data supporting compliance with the
airworthiness requirements are retained.
(a) The operator shall provide, for the use and guidance of maintenance and
operational personnel concerned, a maintenance control manual for the
RPA and RPS, acceptable to the State of Registry, in accordance with the
requirements of this subsection. The design of the manual shall observe
Human Factors principles.
(b) The operator shall ensure that the maintenance control manual is
amended as necessary to keep the information contained therein up to
date.
(d) The operator shall provide the State of the Operator and the State of
Registry with a copy of the operator’s maintenance control manual,
together with all amendments and/or revisions to it and shall incorporate in
it such mandatory material as the State of the Operator or the State of
Registry may require.
10) a description of the RPA and RPS types and models to which the
manual applies;
(a) The operator shall provide, for the use and guidance of maintenance and
operational personnel concerned, maintenance programme(s), approved
by the Authority, containing the information required by 21.10.3.3 for RPA,
the RPS, any ground-based infrastructure and ground-based equipment
under the direct control of the operator. The design and application of the
operator’s maintenance programme shall observe Human Factors
principles.
(c) A maintenance programme for each RPA, each RPS and any ground-
based communication infrastructure as required by 21.11.3.2 shall contain
the following information:
(d) Maintenance tasks and intervals that have been specified as mandatory in
approval of the type design shall be identified as such.
Licences for Remote Pilots will be issued in accordance with the provision
Nig. CARS Part 2.
21.12.1.1 General
(b) RPAS shall meet the performance and equipment carriage requirements
for the specific airspace in which the flight is to operate.
21.12.1.2 C2 Link
(a) RPAS shall have C2 Link equipment that connects the RPS and the RPA
and shall support the following communication tasks:
(1) data commands to modify the flight profile and the configuration of
the RPA;
(2) telemetry data regarding the position, configuration and status of the
RPA;
(c) The RPAS C2 Link system shall be operated only in frequency bands
which are appropriately allocated and protected by the ITU Radio
Regulations.
(b) RPAS pilots shall ensure that ATC is made aware of any operation that
should take place in areas which are likely to affect manned and controlled
air traffic.
(c) RPAS communication with ATC shall be through a very high frequency
(VHF) voice, which may include the requirement to support ATC data link.
Note: The C2 link provide the connection between the remote pilot and the
RPA control and may be considered functionally equivalent to, for
example, the control wires or databus between the cockpit and the
control surfaces possibly via the FCC. The RPA should therefore use
data links that can be assured to meet communication transaction time,
continuity, availability and integrity levels appropriate for the airspace and
operation. SARPs related to these parameters will be needed.
(1) Any RPAS operated in accordance with instrument flight rules shall
have a DAA capability which enables the remote flight crew to avoid
conflicting traffic and other hazards.
(2) DAA shall provide the remote flight crew with the capability of
exercising vigilance for the purpose of detecting and avoiding
potential collisions with other aircraft. The remote flight crew should
exercise vigilance even when air traffic services are provided.
(3) When DAA is used to avoid hazards other than conflicting traffic, its
use should cause no undue hazard to other aircraft or persons or
property on the surface.
(4) DAA shall provide the flight crew with the capability of ensuring
appropriate action is taken when different hazards are present at the
same time, irrespective of whether DAA is provided by one system or
different systems.
(i) The Authority will ensure that the DAA equipment meets the
appropriate airworthiness requirements.
(ii) The Authority will ensure that the operator has carried out a
safety risk assessment of the operations supported by the DAA
equipment, including RPAS controls, displays and alerting
related to DAA as noted above.
(iii) The Authority will ensure that the operator has established and
documented the operational limitations, procedures for the use
of, and training requirements for, the DAA equipment.
(1) The RPA shall be equipped with a DAA system that is capable of
performing automated collision avoidance manoeuvre, except where
the collision avoidance responsibilities of the remote pilot can be
adequately exercised otherwise.
(a) Any person or organization applying as RPAS operator shall undergo and
obtain a Security Clearance and End User Certificate from the appropriate
Security Agency.
(b) An RPAS operator providing services within Nigeria shall develop and
implement a written RPAS Operator Security Programme. A person or
organization shall not operate a Remotely Piloted Aircraft (RPA) within
Nigeria unless he/she has submitted a proposed RPAS Operator Security
Programme for his/her operations to NCAA for approval.
(c) This security programme shall indicate measures and resources employed
to ensure the safeguarding of the RPS/RPA against unlawful interference
during flight or while on ground and the use of RPAS to commit acts of
unlawful interference.
(d) Security measures and technical procedures to protect the C2 link against
unlawful or unintentional interference should also be indicated in the
security programme.
(e) An RPAS operator shall within thirty days of approval of its security
programme ensure that the programme is implemented and in full
operation.
(f) The RPAS operator shall be responsible for the security of their RPS,
facilities, personnel training and for the establishment of procedures to
effectively recognize and respond to acts of unlawful interference against
civil aviation.
(a) When the RPS is installed in a compartment or room, the following shall
apply:
(2) The RPAS operator shall ensure that unauthorized access to RPS is
reasonably prevented and means shall be provided for monitoring
from RPS the entire door area outside the compartment to identify
persons requesting entry and to detect suspicious behaviour or
potential threat.
(3) Develop and implement measures to protect the facility from unlawful
entry (access control)
(a) The RPAS operator shall ensure the physical protection of the RPS when
not in-use.
(a) In the case of portable RPS, the operator shall ensure that.
(1) The RPSs are only released for use to authorized personnel and only
for the time necessary;
(3) When not in use, the RPS shall be stored in a secure place free from
sabotage or unlawful malicious interference
(1) Ensure the Safety and Security of Command and Control (C2) link
which is the data link between the remotely piloted aircraft and the
remote pilot station for the purpose of managing flight. The C2 link
must be free from cyber threat such as hacking, spoofing and other
forms of interference or malicious hijack so as to protect the integrity
of vital components.
(2) Ensure that RPA are stored and prepared for flight in a manner that
will prevent and detect tampering and ensure the integrity of vital
components.
(4) Ensure that no person flies a RPA over any prohibited or restricted
airspace/area/infrastructure such as airports and navigational aids.
(6) Ensure that all RPAS are properly identified with a registration
number
(9) Ensure that records are stored in a manner that ensures protection
from damage, alteration and theft
(2) Ensure that plans are exercised regularly, and post-exercise reviews
should be conducted to ensure operator’s familiarity with the
procedures, and to evaluate the appropriateness of the plans.
(a) Any aerodrome serving RPAS operations shall include in its written airport
security programme measures for RPAS operations appropriate to meet
the requirements of the National Civil Aviation Security Programme
(NCASP)
21.14.1.1 Applicability
(a) This part applies to any manufacturer who intends to get the Authority’s
approval to manufacture RPA and RPS.
(a) To meet the requirements for operations for a specific RPAS, the means of
compliance shall consist of data (tests, analysis, industry consensus
standards) and the results or justification used to demonstrate that the
RPAS meets the predetermined level of safety the Authority has
established as acceptable.
(a) For each model of RPAS that is intended to conduct any operation, the
manufacturer shall provide the Authority with a declaration in accordance
with subsection (1).
(1) the Authority has determined that the model of the RPA does not
meet the terms set out in the means of compliance, or
(2) the manufacturer has notified the Authority of an issue related to the
design of the model under section.
(a) A manufacturer that has made a declaration to the Authority under section
21.14.1.3 shall notify the Authority of any issue related to the design of the
model of the RPAS that results in the system no longer meeting the
technical requirements set out in the means of compliance referred in
subparagraph 21.14.1.22 (b)(2), as soon as possible after the issue is
identified.
21.14.1.5 Documentation
(a) A manufacturer that has made a declaration to the Authority in respect of a
model of a RPAS under section 21.15.1.3 shall make available to each
owner of that model of system:
(1) a maintenance program that includes:
(i) instructions related to the servicing and maintenance of the
system; and
(ii) an inspection program to maintain system readiness;
(2) any mandatory actions the manufacturer issues in respect of the
system;
(3) a RPAS operating manual that includes:
(i) a description of the system;
(ii) the ranges of weights and centers of gravity within which the
system may be safely operated under normal and emergency
conditions and, if a weight and center of gravity combination is
considered safe only within certain loading limits, those load
limits and the corresponding weight and center of gravity
combinations;
(iii) with respect to each flight phase and mode of operation, the
minimum and maximum altitudes and velocities within which
the aircraft can be operated safely under normal and
emergency conditions;
(iv) a description of the effects of foreseeable weather conditions or
other environmental conditions on the performance of both the
system and the RPA;
(v) the characteristics of the system that could result in severe
injury to crew members during normal operations;
(vi) the design features of the system and their associated
operations that are intended to protect against injury to persons
not involved in the operations;
(vii) the warning information provided to the remote pilot in the
event of a degradation in system performance that results in an
unsafe system operating condition;
(2) a current record of the results of and the reports related to the
verifications that the manufacturer has undertaken to ensure
that the model of the system meets the technical requirements
applicable to the operations for which the declaration was
made.
(b) The manufacturer shall keep the records referred to in subsection (a)(1) for
the greater of:
(1) two years following the date that manufacturing of that model of
RPAS permanently ceases, and
(2) the lifetime of the RPA that is an element of the model of system
referred to in paragraph (a).
(a) No RPA shall carry dangerous goods as cargo except by the holder of an
ROC with specific approval to carry dangerous goods or as approved by
the Director General.
(b) RPAS Operators with no specific approval for the transport of dangerous
goods as cargo shall:
(c). RPAS Operators with a specific approval for the transport of Dangerous
goods as cargo shall:
(3) Report to the Authority any occasions when dangerous goods are
discovered to have been carried;
(4) Accept, handle, store, transport, load and unload dangerous goods,
including COMAT classified as dangerous goods as cargo on board
an RPA; and
(d) RPAS Operator shall ensure that all personnel, including third-party
personnel, involved in the acceptance, handling, loading and unloading of
cargo are informed of the operator’s specific approval and limitations with
regards to the transportation of dangerous goods.
(f) RPAS operator shall ensure that security measures or precautions are
taken during the transportation of dangerous goods on board aircraft to
minimize theft or misuse of dangerous goods that may endanger persons,
property or environment.
(g). Transport of Dangerous Goods by air via Remotely Piloted Aircraft (RPA)
shall have the same procedures as aircraft operator as contained in Nig.
CARs (Part 15).
(a) RPAS operators shall establish policies and procedures for the transport of
items in the cargo compartment, which include the conduct of a specific
safety risk assessment. The risk assessment shall include at least the:
(b) The Operator shall establish policies and procedures that address the
items to be transported in the cargo compartment. These shall ensure, to a
reasonable certainty, that in the event of a fire involving those items, it can
be detected and sufficiently suppressed or contained by the elements of
the RPA design associated with cargo compartment fire protection, until
the RPA makes a safe landing.
21.17.1.1 Insurance
(a) Any person conducting operations using RPAS fitted with cameras shall
operate them in a responsible way to respect the privacy of others.
(b) Any person who has a complaint of any operation of an RPAS shall report
to the Authority and the Authority will determine if additional investigation is
required.
APRIL 2023
Address: _______________________________________________________________
2. Description of the applicant’s business organization and corporate structure and name and
address of those entities and individuals having a major financial interest: _____________
________________________________________________________________________
________________________________________________________________________
5. Key Management personnel (Last name, first name, middle name and resume/CV for all
these positions):
7. RPAS/UAV Data
Number of
RPAS/UAV:_____________________________________________________________
Manufactures: ___________________________________________________________
MTOW(Kg) _____________________________________________________________
Payload: _______________________________________________________________
Endurance: ____________________
10. RPAS/UAV Type for which variation is sought state the number of each type to be added:
_______________________________________________________________________
11. In respect of each RPAS/UAV type to be included in the ROC, please indicate the following:
13. Particulars of maintenance personnel including age, nationality, qualification (Ratings and
Currency) and Experience (please attach list)
14. Training arrangements for personnel responsible for supervising the maintenance support for
RPAS/UAV to be included in the ROC (this should be made before introducing the RPAS into
service) – Type of training and number of personnel involved to be stated in respect of the
following:
Management: ___________________________
Supervision: ____________________________
Quality Assurance: _______________________
Arrangement for RPAS/UAV and system familiarization training and related maintenance
practices for maintenance personnel (State type of training and number of maintenance
personnel involved):
15. Provisions for a periodic refresher course and O.J.T Programme (also state frequency)
- Procedures for ensuring that organization responsible for manufacture of each RPAS/UAV
type receives adequate report of occurrences: _____________________
(i) Particulars of operations personnel including age, nationality, qualification (ratings and
currency on assigned RPAS/UAV), and experience (list to be attached)
(ii) Training arrangement for personnel responsible for flight operations of RPAS/UAV to
be included in the ROC (this should be made before introducing the RPAS/UAV into
service) – state type of training and number of personnel involved, including flight crew
and operations personnel (list to be attached)
17. Expatriate quota for foreign staff, if applicable (attach pertinent papers):
i. Location(s) ___________________________
Note: 1. (i) Application for grant of an ROC must be submitted at least 90 days before the date
of intended operation. However, the operations manual must be submitted not less
than 60 days before this date.
(ii) Application for variation of an ROC must be submitted at least 30 days before the
date intended operations.
(iii) Application for the renewal of an ROC must be submitted at least 30 days before the
expiry date of the existing certificate.
2. The Authority must be given at least 10 days prior notice of a proposed change of a
nominated post holder.
3. The fee to be paid for grant or variation of an ROC is as per the latest revision of the Civil
Aviation (fees) Regulations.
……………………………………………………………………….
……………………………………………………………………….
………………………………………………………………………
………………………………………………………………………………………..
…………………………………………………………………………………….....
Address of Operator:
It is hereby certified that the above described RPA has been duly entered into the RPAS
Database of the Nigeria Civil Aviation Authority (NCAA).
IS:21.12.1.2 - (a) The C2 Link shall comply with the following performance requirements:
1) Transaction time: the maximum time for the completion of the operational communication
transaction after which the initiator should revert to an alternative procedure; two values
are specified:
i. RLP nominal time (TT 95%). The maximum nominal time within which 95% of
operational communication transactions is required to be completed
ii. RLP expiration time (ET). The maximum time for the completion of the operational
communication transaction after which the initiator is required to revert to an
alternative procedure.
5) RLP type: A label (e.g. RLP X) that represents the values assigned to RLP parameters
for communication.
6) RLP type allocation: The process of apportioning the various RLP type values to the
various parts of the system.
8) Examples of RPAS C2 functions include all the functions by which a remote pilot is
effectively having control over the RPA navigation, attitude and the RPA airborne
systems.
9) RLTP (Required Link Technical Performance): The technical transit time for C2 data
delivery that does not include the human (or the automatic response system) times for
message composition, operational response by human operator (or automatic system),
and recognition of the operational response.
10) RLTPX: The maximum time allocated to the critical transit times for a C2 message,
allocated to system X.
Note.— An electronic copy of the ROC is required to be carried on board the RPS (see
21.10.2.1(f)).
Notes.—
1. For use of the State of the Operator.
2. Replace by the name of the State of the Operator.
3. Replace by the identification of the issuing authority of the State of the Operator.
4. Unique ROC number, as issued by the State of the Operator.
5. Date after which the ROC ceases to be valid (dd-mm-yyyy).
6. Replace by the operator’s registered name.
7. Operator’s trading name, if different. Insert “dba” before the trading name (for “doing
business as”).
8. Operator’s principal place of business address.
9. Operator’s principal place of business telephone details, including the country code. Email
to be provided if available.
10. The contact details include the telephone numbers, including the country code, and the
email address (if available) at which operational management can be contacted without
undue delay for issues related to flight operations, airworthiness, remote flight crew
competency, dangerous goods and other matters, as appropriate.
11. Insert the controlled document, carried on board, in which the contact details are listed, with
the appropriate paragraph or page reference, e.g.: “Contact details are listed in the
operations manual, Gen/Basic, Chapter 1, 1.1” or “… are listed in the operations
specifications, page 1” or “… are listed in an attachment to this document”.
12. Operator’s registered name.
13. Insertion of reference to the appropriate civil aviation regulations.
14. Issuance date of the ROC (dd-mm-yyyy).
15. Title, name and signature of the authority representative. In addition, an official stamp may
be applied on the ROC.
For each RPA model in the operator’s fleet, identified by aircraft make, model and variant,
the following information shall be included:
d) RPA model;
e) RPS model;
Note — If specific approvals and limitations are identical for two or more models, these
models may be grouped in a single list.
OPERATIONS SPECIFICATIONS
( subject to the approved conditions in the Operations manual )
Types of Operation6:
Area(s) of operation7:
Special limitations8:
SPECIAL AUTHORIZATIONS YES NO DESCRIPTION9 REMARKS
Dangerous goods
Low Visibility Operations:
CAT10: RVR: ___m DH____ ft
Approach and Landing
RVR 11_______ m
Take-off
12
Operational Credits
VLOS13
BVLOS14
RLOS15
BRLOS16
AR Navigation Specifications 17
for PBN authorizations
Continuing Airworthiness 18
Others19
Notes.—
1. Telephone and contact details of the authority, including the country code. Email to be
provided if available.
3. Insert the operator’s registered name and the operator’s trading name, if different. Insert
“dba” before the trading name (for “doing business as”).
4. Issuance date of the operations specifications (dd-mm-yyyy) and signature of the authority
representative
5. Insert the Commercial Aviation Safety Team (CAST)/ICAO designation of the RPA make,
model and series, or master series, if a series has been designated. The CAST/ICAO
taxonomy is available at: http://www.intlaviationstandards.org/. Note— there could be
multiple entries in this section
6. Very high level (VHL) operations above FL 600, aerial work, long duration flight, commercial
transport, etc.
8. List the applicable special limitations (e.g. day-only, population density and altitude
limitations).
9. List in this column the most permissive criteria for each specific approval (with appropriate
criteria).
10. Insert the applicable precision approach category (e.g. CAT II, III). Insert the minimum RVR
in metres and decision height in feet. One line is used per listed approach category.
11. Insert the approved minimum take-off RVR in metres, or the equivalent horizontal visibility
if RVR is not used. One line per approval may be used if different approvals are granted.
17. Performance-based navigation (PBN): one line is used for each PBN AR navigation
specification approval (e.g. RNP AR APCH), with appropriate limitations listed in the
“Description” column.
18. Insert the name of the person/organization responsible for ensuring that the continuing
airworthiness of the RPAS is maintained and the regulation that requires the work, i.e. within
the ROC regulation or a specific approval.
19. Other authorizations or data can be entered here, using one line (or one multi-line block)
per authorization (e.g. special approach authorization, approved navigation performance)
IS: 21.10.6.23 The operations manual shall contain at the least the following:
(1) General
(i) policies pertaining to flight time, flight duty period, duty period limitations
and rest requirements for remote flight crew members in accordance with
section 21.10.26.1; and
Note.— Instructions on the use of autopilots and auto-throttles, together with (24) and (28), are
essential for avoidance of approach and landing accidents and controlled flight into terrain
accidents.
Note.— Procedures for the operation of ACAS are contained in PANS-OPS (Doc 8168),
Volume I, and in PANS-ATM (Doc 4444), Chapters 12 and 15.
(30) Information and instructions relating to the interception of civil RPA including:
a) procedures, as prescribed in Annex 2, for remote pilots-in-command of
intercepted aircraft; and b) visual signals for use by intercepting and
intercepted aircraft, as contained in Annex 2.
(31) For RPA intended to be operated above 15 000 m (49 000 ft.), procedures in
the event that a decision to descend is taken, covering:
i) the necessity of giving the appropriate ATS unit prior warning of the
situation and of obtaining a provisional descent clearance; and
ii) the action to be taken in the event that communication with the ATS unit
cannot be established or is interrupted.
(32) Details of the safety management system (SMS) provided in accordance with
Appendix 2 to Annex 19.
Note.— Guidance material on the development of policies and procedures for dealing with
dangerous goods incidents on board aircraft is contained in Emergency Response Guidance
for Aircraft Incidents Involving Dangerous Goods (Doc 9481).
(2) The normal, abnormal and emergency procedures to be used by the remote
flight crew and the checklists relating thereto as required by section 21.10.28
of these Regulations.
(3) Operating instructions and information on climb performance with all engines
operating, if provided in accordance with this section.
(4) Flight planning data for pre-flight and in-flight planning with different
thrust/power and speed settings.
(5) The maximum crosswind and tailwind components for each RPA type
operated and the reductions to be applied to these values having regard to
gusts, low visibility, runway surface conditions, remote crew experience, use of
autopilot, abnormal or emergency circumstances, or any other relevant
operational factors.
(6) Instructions and data for mass and balance calculations.
(7) Instructions for RPA loading and securing of load.
(8) RPAS systems, associated controls and instructions for their use, as required
by section 21.10.28 of this Regulations.
(9) The minimum equipment list and configuration deviation list for the RPA types
operated and specific operations authorized, including any requirements
relating to operations where performance-based navigation is prescribed.
Checklist of emergency and safety equipment and instructions for its use.
(10) Emergency evacuation procedures for the RPS, including type-specific
procedures, remote crew coordination, assignment of remote crew’s
emergency positions and the emergency duties assigned to each remote crew
member.
(11) Procedures to mitigate at least the emergencies and contingencies as required
by section 21.14.1.7 of this Regulations.
(1) A route guide to ensure that the remote flight crew will have, for each flight,
information relating to communication facilities, navigation aids, aerodromes,
instrument approaches, instrument arrivals and instrument departures as
applicable for the operation, and such other information as the operator may
deem necessary for the proper conduct of flight operations.
(2) The minimum flight altitudes for each route to be flown.
(3) Aerodrome operating minima for each of the aerodromes that are likely to be
used as aerodromes of intended landing or as alternate aerodromes.
(4) The increase of aerodrome operating minima in case of degradation of
approach or aerodrome facilities.
(5) The necessary information for compliance with all flight profiles required by
regulations, including but not limited to, the determination of:
(i) for remotely piloted aircraft, take-off runway length requirements for dry, wet
and contaminated conditions, including those dictated by system failures
which affect the take-off distance;
(ii) take-off climb limitations;
(iii) en-route climb limitations;
(iv) approach climb limitations and landing climb limitations;
(v) for remotely piloted aircraft, landing runway length requirements for dry,
wet and contaminated conditions, including systems failures which affect
the landing distance; and
(vi) supplementary information, such as tire speed limitations.
(e) Training
(1) Details of the remote flight crew training programme, as required by Nig. CARs
Part 8.10.1.15 and IS:8.10.1.15.
The operator shall include within the operations manual the following details for all RPS that
it operates:
(b) the RPS manufacturer and manufacturer’s designation for the RPS;
(d) indication of the type, model and variant of each RPA an RPS is capable of
controlling; and