FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19WA272 · Reims Aviation Cessna F172N

14 Aug 2019 Possible conflict · Lesnovo, Bulgaria

Reims Aviation Cessna F172N · Incident: loss of engine power (total) on approach

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's date. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN19WA272
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Unknown · led by another country; figures from NTSB notifications
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Unknown
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Not recorded

Reims Aviation Cessna F172N

Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
LZ-SPB
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Unknown
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern final
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power (total)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On August 14, 2018, about 0750 coordinated universal time, a Reims Aviation Cessna F172N airplane, Bulgarian registration number LZ-SPB, had a forced landing at the Lesnovo Airport (LBLS), Lesnovo, Bulgaria, following an inflight loss of engine power. The airplane sustained engine damage. The two pilots were uninjured. The local flight originated from LBLS.The accident investigation is under the jurisdiction and control of the Bulgarian government. This report is for informational purposes only and contains only information released by or obtained from the Bulgarian government. Further information pertaining to this accident may be obtained from:

Ministry of Transport, Information Technology and Communications Aircraft Accident Investigation Unit 9 Diakon Ignatii Str., 1000 Sofia, Bulgaria

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record CEN19WA272
Event ID
20190819X03300
Case number
CEN19WA272
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: coordinates, damage. Values present in the bulk record are kept.
  • The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: 06c59a0f5f085702c4e62e68454d2515fb75782226d40d6beaf1afba41c34201; retrieved 2026-09-16T09:47:14.694Z.