Pelican Airways Aero Commander 100-180 accident
Aero Commander 100-180 · Accident: airframe, component or system failure en route
From Pitt-Greenville Airport (PGV) to 8W5
Event
- NTSB case
- ATL95LA152
- 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
- 0
- 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
- Charter & commuter
- 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
Aero Commander 100-180
- Aircraft type
- Aero Commander 100
- 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
- N4066X
- Operator
- Pelican Airways
- Onboard fatalities
- Unknown
- Route
- From Pitt-Greenville Airport (PGV), Greenville, NCTo 8W5
- 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
- Part 135: Air Taxi & Commuter
- 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
- En route · cruise
- First occurrenceThe 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
- Airframe, component or system failure
- 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
- Window, flight compartment window/windshield › Burst
Approximate · Estimated position: the centre of Ocracoke, NC, the place the record names. Not the accident site.
NTSB narrative
While in cruise flight over marshy terrain, the center portion of the aircraft's windshield imploded, forcing open the cabin door. The pilot was unable to maintain altitude and could not glide to dry land, therefore he elected to force land in the salt marsh. During the Landing roll, the aircraft nosed over. According to the passengers, when they boarded the airplane they noted that the windscreen was cracked. However, the crack was adjacent to a door post, not the center of the windscreen. Initially, the pilot believed that the airplane had been struck by a bird. Postaccident examination of the wreckage did not reveal any evidence of a bird strike. A similar windscreen implosion occurrence, involving the same make and model airplane, was located in the FAA's Service Difficulty Reports. The report stated that during level flight the upper half of the windshield broke away, first inward, then the pilot pushed it outward. Aircraft control was affected, and a forced landing was accomplished, without causing substantial damage.
Probable cause
A SHATTERED WINDSHIELD WHICH PRECLUDED MAINTAINING LEVEL FLIGHT DUE TO INCREASED AERODYNAMIC DRAG.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL95LA152
- Event ID
- 20001207X04150
- Case number
- ATL95LA152
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: bbb059ec0e080ffd03ec681d133a8488016effa83baf1e03ef1e400b084d1ec9; retrieved 2026-09-18T17:58:16.626Z.