Aberdeen Flying Service Cessna T303 accident
Cessna T303 · Accident: structural icing en route
From Aberdeen Regional Airport (ABR) to Pine Ridge, SD
Event
- NTSB case
- CEN18LA146
- 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
- Charter & commuter
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Cessna T303
- Aircraft type
- Cessna 303
- 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
- N9746C
- Operator
- Aberdeen Flying Service
- Onboard fatalities
- Unknown
- Route
- From Aberdeen Regional Airport (ABR), Aberdeen, SDTo Pine Ridge, SD
- Aircraft age
- About 35 years (built 1983)
- 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 · descent
- 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
- Structural icing
- 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
- Aircraft › Aircraft structures
- Environmental issues › Conditions/weather/phenomena
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before the air taxi flight, the commercial pilot obtained a weather briefing via the company computer system and reviewed the weather information with the company chief pilot. The pilot stated that based on the computer briefing, which did not include icing conditions, he was aware of the forecasted weather conditions along the route of flight and at the intended destination. However, the briefing was incomplete as it did not contain any in-flight weather advisories, which would have alerted the pilot of moderate icing conditions expected over the flight route in the form of AIRMET Zulu.
After takeoff and during the climb to 12,000 ft mean sea level (msl), the airplane encountered light rime ice, and the pilot activated the de-ice equipment with no issues noted. After hearing reports of better weather at a lower altitude, the pilot requested a descent to between 5,000 and 6,000 ft. During the descent to 6,000 ft msl and with the airplane clear of ice, the airplane encountered light to moderate icing conditions. The pilot considered turning back to another airport but could not get clearance until the airplane was closer to his destination. Shortly thereafter, the pilot stated that it felt “like a sheet of ice fell on us” as the airplane encountered severe icing conditions. The pilot applied full engine power in an attempt to maintain altitude. The airplane exited the overcast cloud layer about 500 ft above ground level. The pilot chose to execute an off-airport emergency landing because the airplane could not maintain altitude. During the landing, the landing gear separated; the airplane came to rest upright and sustained substantial damage to the wings and fuselage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation and that the airplane was within its maximum gross weight.
Structural icing was observed on the airframe after the landing. Based on the weather information, which indicated the probability of icing between 5,000 and 9,000 ft over the region and a high threat of supercooled large droplets between 5,000 and 7,000 ft, it is likely that the airplane, which was equipped for flight in icing conditions, inadvertently encountered severe icing conditions consistent with supercooled large droplets, which resulted in structural icing that exceeded the airplane’s capabilities to maintain altitude.
Probable cause
The airplane’s inadvertent encounter with severe icing conditions during descent, which resulted in structural icing, the pilot’s inability to maintain altitude, and an emergency landing. Contributing to the accident was an incomplete preflight weather briefing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18LA146
- Event ID
- 20180424X33220
- Case number
- CEN18LA146
- 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: 8f344005e9dcff4085e5bf2195a291b439b8e1e1f8152c019159161ac8cd8143; retrieved 2026-09-16T06:55:38.291Z.