FORCETALLY
Loading the evidence…
Preparing your view.
Preparing your view.
Drones & UAVsIn serviceProfile in progress
Unmanned aerial vehicle
Lihiniya MK I is a unmanned aerial vehicle originating in Sri Lanka. It was built by Sri Lanka Air Force Centre for Research and Development. Reported operators include Sri Lanka Air Force.
Sri LankaNo check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
No check recorded yet.
Unmanned aerial vehicle
Sri Lanka
Sri Lanka Air Force Centre for Research and Development
Sri Lanka Air Force
Lihiniya MK II
115 lb (52 kg)
19 liter
1 × Hirth 4103 two-stroke, air cooled, opposed engine, 8 hp (6.0 kW)
60 kn (69 mph, 110 km/h) For Phase 1
10.8 nmi (12.4 mi, 20.0 km)
7 hours
10,000 ft (3,000 m)
Reference text from Wikipedia contributors, used under CC BY-SA 4.0.
Lihiniya MK I equipment records. Variants, orders and quantities are shown as reported in each inventory source; coverage is incomplete.
Sri LankaReported count for Lihiniya MK I /MK II · MK IE. Service scope: Sri Lanka Air Force; does not replace a national total. 1 distinct quantity component(s) from the same source list; shared rowspan cells counted once. Explicit source inventory scope: active; no other stock status or total inferred. Count column(s): in service: 2. Origin: Sri Lanka. The listed variants/roles are the scope, not an immediately deployable count. The components do not establish one inventory census date; the stored date is the retrieved source snapshot.
Reported count for Lihiniya MK I /MK II · MK IE. Service scope: Sri Lanka Air Force; does not replace a national total. 1 distinct count cell(s) from the same source list; shared rowspan cells counted once. Retired, wholly reserve and on-order rows are excluded; the reported count retains any explicitly mixed stock scope in the quoted row. Count column(s): in service: 2. Origin: Sri Lanka. The listed variants/roles are the scope, not an immediately deployable count. The components do not establish one inventory census date; the stored date is the retrieved source snapshot.