FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA18CA069 · Weaver David A PULSAR 912XP

2 Dec 2017 · Plato Center, IL, United States

Weaver David A PULSAR 912XP · Accident: controlled flight into terrain/object (CFIT) on approach

From Lawrenceville Vincennes International Airport (LWV) to Olson Airport (LL53)

Report a problem

Event

NTSB case
GAA18CA069
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
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
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
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Weaver David A PULSAR 912XP

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
N912GR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lawrenceville Vincennes International Airport (LWV), Lawrenceville, ILTo Olson Airport (LL53), Plato Center, IL
Aircraft age
About 22 years (built 1995)
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
Part 91: General Aviation
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
Controlled flight into terrain/object (CFIT)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Action/decision
  • Personnel issues › Psychological

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

NTSB narrative

The pilot reported that, while making a straight-in approach to a private airport just after dusk, but before dark, he attempted to activate the pilot-controlled lighting (PCL) but was unsuccessful. He added that he continued toward the airport, and while maneuvering for landing, he lost sight of the airport. The pilot did not regain visual reference of the airport during the landing descent, and the airplane impacted a fence adjacent to the runway.

The airplane sustained substantial damage to the fuselage.

The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

The airport owner reported that the PCL antenna required line-of-sight with the aircraft to operate the PCL system. Due to the antenna's position and hangars on the airport, the antenna did not receive signals from the southeast, the direction from which the accident airplane was approaching. He added that, because the airport was private, he could not issue a NOTAM to describe the operation of the runway lights.

Probable cause

The pilot’s decision to continue to land without visual reference to the airport in low light conditions. Contributing to the accident was the pilot’s inability to activate the private airport’s pilot-controlled lighting system due to its configuration.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA069
Event ID
20171206X84125
Case number
GAA18CA069
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: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: a9d2f891d7d1bd29c8b331b72096bc38219faceebfbea5e93254826f3623bcb5; retrieved 2026-09-16T06:05:49.761Z.