GAA18CA258 · Berger Bernard M PULSAR SERIES III
Berger Bernard M PULSAR SERIES III · Accident: abnormal runway contact during landing
From Carlisle Airport (N94) to Carlisle Airport (N94)
Event
- NTSB case
- GAA18CA258
- 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
Berger Bernard M PULSAR SERIES III
- Aircraft type
- Berger Bernard PULSAR
- 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
- N914BB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Carlisle Airport (N94), Carlisle, PATo Carlisle Airport (N94), Carlisle, PA
- Aircraft age
- About 16 years (built 2002)
- 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
- Landing · flare/touchdown
- 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during the preflight inspection, he observed no discrepancies and noted that the oil level was "inside the lower bound of normal oil capacity." He reported that en route, the oil pressure "was in the 30s [pounds per square inch] and trending downward" but still within the normal engine oil pressure limits. He decided to divert to a nearby airport as a precaution.
The pilot reported that, while maneuvering to the alternate airport, the engine instruments appeared normal. However, during left base for the runway, he observed "a few seconds of white smoke" coming from the engine over the left wing. He reduced power, added flaps, and noticed that the airplane's approach speed was too fast. He decided he would not attempt a go-around due to the smoke and shut the engine off "thinking of the possibility of an engine fire." Subsequently, the airplane bounced during the initial touchdown and landed near the runway's halfway point. The pilot applied brakes, but the airplane overran the runway into a dirt field, and the nose landing gear collapsed.
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.
Probable cause
The pilot’s failure to maintain an appropriate approach speed, which resulted in a bounced landing and a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA258
- Event ID
- 20180503X65158
- Case number
- GAA18CA258
- 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. 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: c7f135a26ff0482fa9af9f485ebd70fca41b481c43d236c98c20ff53f4ebaa30; retrieved 2026-09-16T07:00:30.300Z.