Dokumendiregister | Transpordiamet |
Viit | 13.11-4/24/3465-10 |
Registreeritud | 15.07.2024 |
Sünkroonitud | 17.07.2024 |
Liik | Kooskõlastus / kinnitus / heakskiitmine |
Funktsioon | 13.11 Mehitamata õhusõidukite lennutamise korraldamine |
Sari | 13.11-4 Erikategooria omistamise dokumendid |
Toimik | 13.11-4/2024 |
Juurdepääsupiirang | Avalik |
Juurdepääsupiirang | |
Adressaat | |
Saabumis/saatmisviis | |
Vastutaja | Marko Liiva (Users, Lennundusteenistus, Mehitamata õhusõidukite osakond) |
Originaal | Ava uues aknas |
TRANSPORDIAMETI JUHTIMISSÜSTEEM OT_264_K1_V3_r1
OPERATIONAL AUTHORISATION FOR THE `SPECIFIC`CATEGORY
Kinnitamine: 27.02.2023 nr 1.1-7/23/27 1/5
Data protection: the competent authority processes the personal data submitted in the application in accordance
with Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons in the processing of personal data and on the free movement of such data and on the repeal of
Directive 95/46/EC (protection of personal data general regulation). The competent authority processes personal
data for the purposes of filling out the request, managing it and taking follow-up measures in accordance with Article 12 of Regulation (EU) 2019/947 of 24 May 2019 on the rules and procedures for the operation of
unmanned aircraft.
If the applicant needs additional information about the processing of their personal data or the exercise of their rights (for example, to access or correct inaccurate or incomplete data), they must contact the contact point of
their competent authority.
The applicant has the right to file a complaint with the national data protection authority regarding the processing of his personal data at any time.
1. Authority that issues the authorisation
1.1 Issuing authority Estonia
1.2 Point of contact
Name
Telephone
Marko Liiva
Senior Inspector of Unmanned Aviation Department
+372 58050 1307
2. UAS operator data
2.1 UAS operator registration number ESTjf4ey66bczk0d
2.2 UAS operator name Hepta Group Airborne OÜ
2.3 Operational point of contact
Name
Telephone
Mathias Tammeveski
+372 5484 0844
3. Authorised operation
3.1 Authorised location(s) According to PDRA and its compliance table
3.2 Extent of the adjacent area 5 km
3.3 Risk assessment reference and revision SORA version __ PDRA #S-01 other _________
3.4 Level of assurance and integrity SAIL II
3.5 Type of operation VLOS BVLOS
3.6 Transport of dangerous goods Yes No
3.7 Ground risk
characterisation
3.7.1 Operational area Populated area
3.7.2 Adjacent area Populated area
3.8 Ground risk
mitigations
3.8.1 Strategic mitigations No Yes, low Yes, medium Yes,
high
3.8.2 ERP No Yes, low Yes, medium Yes,
high
3.9 Height limit of the operational volume 150 m (500 ft) if mitigations in place
3.10 Residual air risk
level
3.10.1 Operational volume ARC-a ARC-b ARC-c ARC-d
3.10.2. Adjacent volume ARC-a ARC-b ARC-c ARC-d
3.11.1 Strategic mitigations No Yes
TRANSPORDIAMETI JUHTIMISSÜSTEEM OT_264_K1_V3_r1
OPERATIONAL AUTHORISATION FOR THE `SPECIFIC`CATEGORY
Kinnitamine: 27.02.2023 nr 1.1-7/23/27 2/5
3.11 Air risk
mitigations
OM 3.5
3.11.2 Tactical mitigation
methods OM 3.5
3.12 Achieved level of containment Basic Enhanced
3.13 Remote pilot competency OM 3.4
3.14 Competency of staff, other than the remote pilot,
essential for the safety of the operation OM 3.4
3.15 Type of events to be reported to the competent
authority (in addition to those required by
Regulation (EU) No 376/2014)
OM 3.4
3.16 Insurance No Yes
3.17 Operations manual reference Operations Manual issue 3, revision 2
3.18 Compliance evidence file reference OM Appendix 7
3.19 Remarks / additional limitations
4. Data of authorised UAS
4.1 Manufacturer DJI 4.2 Model M300RTK
Mavic 3T
4.3 Type of UAS
Aeroplane Helicopter
Multirotor
Hybrid/VTOL Lighter
than air / other
4.4 Maximum
characteristic
dimensions
M300: 0.81m
Mavic 3T: 0.380m
4.5 Take-off mass M300: 9kg
Mavic 3T: 1.05kg 4.6 Maximum speed
M300: 23 m/s (45 kt)
Mavic 3T: 21 m/s (39 kt)
4.7 Additional technical requirements
4.8 Serial number or, if applicable, UA registration
mark
M300: 1ZNBHC200C0071, 1ZNBJ3A00C00MT,
1ZNBJ5700C00NN
Mavic 3T: 1581F5FJD235Q00D65UH,
1581F5FJD237K00D3T4B,
1581F5FJD238100D1X71
4.9 Number of type certificate (TC) or design
verification report, if required n/a
4.10 Number of the certificate of airworthiness
(CofA), if required n/a
4.11 Number of the noise certificate, if required n/a
4.12 Mitigation to reduce effect of ground impact No Yes, low Yes, medium Yes, high
Required to reduce the ground risk Yes No
4.13 Technical requirements for containment Basic Enhanced
5. Remarks
TRANSPORDIAMETI JUHTIMISSÜSTEEM OT_264_K1_V3_r1
OPERATIONAL AUTHORISATION FOR THE `SPECIFIC`CATEGORY
Kinnitamine: 27.02.2023 nr 1.1-7/23/27 3/5
6. Operational authorisation
Hepta Group Airborne OÜ is authorised to conduct UAS operations with the UAS(s) defined in Section 4 and according
to the conditions and limitations defined in Section 3, for as long as it complies with this operational authorisation, with
Regulation (EU) 2019/947, and with any applicable Union and national regulations related to privacy, data protection,
liability, insurance, security, and environmental protection.
6.1 Operational authorisation number EST-OAT-0002/002
6.2 Expiry date 09/01/2027
Date
15/07/2024
Signed digitally
Instructions for filling in the operational authorisation form
1.1 Name of the competent authority that issues the operational authorisation, including the name of the State.
1.2 Contact details of the competent authority staff responsible for the file.
2.1 UAS operator registration number in accordance with Article 14 of the UAS Regulation.
2.2 UAS operator’s name, as registered in the UAS operator registration database.
2.3 Contact details of the person responsible for the UAS operation, in charge to answer possible operational questions
raised by the competent authority.
3.1 Location(s) where the UAS operator is authorised to operate. The identification of the location(s) should contain
the full operational volume and ground risk buffer (the red line in Figure 2). Depending on the initial ground and
air risk and on the application of mitigation measures, the location(s) may be ‘generic’ or ‘precise’ (refer to GM2
UAS.SPEC.030(2)). When the UAS operation is conducted in a MS other than the State of registration, the
competent authority of the MS of registration should specify the location(s) only after receiving confirmation from
the State of operation, according to Article 13 of the UAS Regulation.
Figure 2 — Operational area and ground risk buffer
3.2 Provide the maximum distance in km to be considered for the adjacent area, starting from the limits of the ground
risk buffer.
3.3 Select one of the three options. If the SORA is used, indicate the version. In case a PDRA is used, indicate the
number and its revision. In case a risk assessment methodology is used other than the SORA, provide its reference.
In this last case, the UAS operator should demonstrate that the methodology complies with Article 11 of the UAS
Regulation.
Operational area
Ground risk buffer
Adjacent area Adjacent
area
TRANSPORDIAMETI JUHTIMISSÜSTEEM OT_264_K1_V3_r1
OPERATIONAL AUTHORISATION FOR THE `SPECIFIC`CATEGORY
Kinnitamine: 27.02.2023 nr 1.1-7/23/27 4/5
3.4 If the risk methodology used is the SORA, indicate the final SAIL of the operation, otherwise the equivalent
information provided by the risk assessment methodology used.
3.5 Select one of the two options.
3.6 Select one of the two options.
3.7 Characterise the ground risk (i.e. density of overflown population density, expressed in persons per km2, if
available, or ‘controlled ground area’, ‘sparsely populated area’, ‘populated area’, ‘gatherings of people’) for both
the operational and the adjacent area.
3.8.1 Select one of the four options. In case the risk assessment is based on the SORA, this consists in
M1 mitigation.
3.8.2 Select one of the four options. In case the risk assessment is based on the SORA, this consists in
M3 mitigation.
3.9 Insert the maximum flight altitude, expressed in metres and feet in parentheses, of the approved operational volume
(adding the air risk buffer, if applicable) using the AGL reference when the upper limit is below 150 m (492 ft),
or use the MSL reference when the upper limit is above 150 m (492 ft).
3.10 Select one of the four options.
3.11.1 Select one of the two options.
3.11.2 Describe the tactical mitigation methods to be applied by the UAS operator.
3.12 Select one of the two options.
3.13 Specify the type of the remote pilot certificate, if required; otherwise, indicate ‘Declared’.
3.14 Specify the type of the certificate for the staff, other than the remote pilot, essential for the safety of the operation,
if required; otherwise, indicate ‘Declared’.
3.15 List the type of events that the UAS operator should report to the competent authority, in addition to those required
by Regulation (EU) No 376/2014, if applicable.
3.16 Select one of the two options.
3.17 Indicate the OM’s identification and revision number.
3.18 Indicate the compliance evidence file identification and revision number.
3.19 Additional limitations defined by the competent authority.
4 Only the UAS features/characteristics required to be used for the operation should be identified in the form (e.g.
in case the UAS qualifies for enhanced containment but the operation requires a basic containment, and the
operator developed consistent procedures, then the basic containment should be ticked).
4.1 Name of the manufacturer of the UAS.
4.2 Model of the UAS as defined by the manufacturer.
4.3 Select one of the five options.
4.4 Indicate the maximum dimensions of the UA in metres (e.g. for aeroplanes: the length of the wingspan; for
helicopters: the diameter of the propellers; for multirotors: the maximum distance between the tips of two opposite
propellers) as used in the risk assessment to identify the ground risk.
4.5 Indicate the maximum value, expressed in kg, of the UA take-off mass (TOM), at which the UAS operation may
be operated. All flights should then be operated not exceeding that TOM. The TOM maybe be different from
(however, not higher than) the MTOM defined by the UAS manufacturer.
TRANSPORDIAMETI JUHTIMISSÜSTEEM OT_264_K1_V3_r1
OPERATIONAL AUTHORISATION FOR THE `SPECIFIC`CATEGORY
Kinnitamine: 27.02.2023 nr 1.1-7/23/27 5/5
4.6 Maximum cruise airspeed, expressed in m/s and kt in parentheses, as defined in the manufacturer’s instructions.
4.7 List any additional technical requirements established by the competent authority.
4.8 Unique serial number (SN) of the UA defined by the manufacturer according to standard ANSI/CTA-2063-A-
2019, Small Unmanned Aerial Systems Serial Numbers, 2019, or the UA registration mark if the UA is registered.
In case of privately built UAS or UAS not equipped with a unique SN, insert the unique SN of the remote
identification system.
4.9 Include the EASA TC number, or the UAS design verification report number issued by EASA, as required by the
competent authority.
4.10 If a UAS with an EASA TC is required, the UAS should have a certificate of airworthiness (CofA) and the
competent authority should require compliance with the continuing airworthiness rules.
4.11 If a UAS with an EASA TC is required, the UAS should have a noise certificate.
4.12 Select one of the four options of the first row. In case the risk assessment is based on the SORA, this consists in
M2 mitigation. Even if the UAS may be equipped with such system, this mitigation may not be required in the
operation to reduce the ground risk. In this case, in the second row select ‘NO’. If the mitigation is instead used to
reduce the ground risk, select ‘YES’ and the operator is required to include in the OM the related procedures.
4.13 Select one of the two options.
5 Free-text field for the addition of any relevant remark.
6.1 Reference number of the operational authorisation, as issued by the competent authority. The number should have
the following format:
NNN-OAT-xxxxx/yyy
Where:
— ‘NNN’ is the ISO 3166 Alpha-3 code of the Member State that issues the operational authorisation;
— ‘OAT’ is a fixed field meaning ‘operational authorisation’;
— ‘xxxxx’ are up to 12 alphanumeric characters defining the operational authorisation number; and
— ‘yyy’ are 3 alphanumeric characters defining the revision number of the operational authorisation; each
amendment of the operational authorisation will determine a new revision number.
6.2 The duration of the operational authorisation may be unlimited; in this case, indicate ‘Unlimited’.
The authorisation will be valid for as long as the UAS operator complies with the relevant requirements of the
UAS Regulation and with the conditions defined in the operational authorisation.
Note 1: In section 4, more than one UAS may be listed. If needed, the fields may be duplicated.
Note 2: The signature and stamp may be provided in electronic form. The quick response (QR) code should provide the
link to the national database where the operational authorisation is stored.
Nimi | K.p. | Δ | Viit | Tüüp | Org | Osapooled |
---|---|---|---|---|---|---|
Kiri | 15.07.2024 | 2 | 13.11-4/24/3465-7 | Kooskõlastus / kinnitus / heakskiitmine | transpordiamet | |
Kiri | 15.07.2024 | 2 | 13.11-4/24/3465-7 | Kooskõlastus / kinnitus / heakskiitmine | transpordiamet | |
Kiri | 15.07.2024 | 2 | 13.11-4/24/3465-11 | Kooskõlastus / kinnitus / heakskiitmine | transpordiamet | |
Kiri | 15.07.2024 | 2 | 13.11-4/24/3465-11 | Kooskõlastus / kinnitus / heakskiitmine | transpordiamet | |
Kiri | 15.07.2024 | 2 | 13.11-4/24/3465-8 | Kooskõlastus / kinnitus / heakskiitmine | transpordiamet | |
Kiri | 15.07.2024 | 2 | 13.11-4/24/3465-8 | Kooskõlastus / kinnitus / heakskiitmine | transpordiamet | |
Kiri | 15.07.2024 | 2 | 13.11-4/24/3465-9 | Kooskõlastus / kinnitus / heakskiitmine | transpordiamet | |
Kiri | 15.07.2024 | 2 | 13.11-4/24/3465-9 | Kooskõlastus / kinnitus / heakskiitmine | transpordiamet | |
Kiri | 15.07.2024 | 2 | 13.11-4/24/3465-6 | Kooskõlastus / kinnitus / heakskiitmine | transpordiamet | |
Kiri | 15.07.2024 | 2 | 13.11-4/24/3465-6 | Kooskõlastus / kinnitus / heakskiitmine | transpordiamet | |
Kiri | 15.07.2024 | 2 | 13.11-4/24/3465-10 | Kooskõlastus / kinnitus / heakskiitmine | transpordiamet | |
Hepta Group Airborne OÜ tähtajalise käitamisloa muutmine | 12.07.2024 | 3 | 1.1-2/24/88 | Otsus | transpordiamet | |
Kiri | 10.06.2024 | 35 | 13.11-4/24/3465-5 🔒 | Sissetulev kiri | transpordiamet | Hepta Airborne |
Kiri | 21.05.2024 | 55 | 13.11-4/24/3465-4 🔒 | Valjaminev kiri | transpordiamet | |
Kiri | 02.05.2024 | 74 | 13.11-4/24/3465-3 🔒 | Valjaminev kiri | transpordiamet | Hepta Airborne |