FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Aero Air Bombardier Learjet CORP. 35A incident

5 Mar 2012 · Anchorage, AK, United States

Bombardier Learjet CORP. 35A · Incident: loss of control on ground during landing

From Kenai Municipal Airport (PAEN) to Ted Stevens Anchorage International Airport (PANC)

Report a problem

Event

NTSB case
ANC12IA024
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
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
Visual Meteorological Cond

Bombardier Learjet CORP. 35A

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
N544LM
Operator
Aero Air
Onboard fatalities
Unknown
Route
From Kenai Municipal Airport (PAEN), Kenai, AKTo Ted Stevens Anchorage International Airport (PANC), Anchorage, AK
Aircraft age
About 30 years (built 1982)
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
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
Loss of control on ground
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft systems
  • Environmental issues › Physical environment

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

As the medical transport flight descended below the cloud cover during dark night, instrument meteorological conditions while on approach, the flight crew discovered that the first officer's windscreen was entirely covered with ice and that she would not be able to continue the approach. Although the captain's windscreen was partially covered with ice, he could still see the runway, so he took control of the airplane and continued the approach. The flight crew then confirmed that the windscreen heating and alcohol anti-ice systems were on. As the airplane passed over the runway threshold, the captain's windscreen abruptly iced over, and he had no forward visibility as the airplane's main landing gear wheels touched down. Unable to see the runway ahead and with limited visibility to each side, the flight crew attempted to activate the engine thrust reversers to slow the landing roll, but the airplane subsequently veered to the right of the runway centerline, and the right wing collided with a snow berm. The pilots reported no preincident mechanical malfunctions or failures that would have precluded normal operation.

About 15 minutes before the incident, the approach controller at an airport about 7 miles northeast of the incident airport advised the destination airport's north radar position controller that the pilot of another airplane had reported that he was "going around" due to severe icing on the airplane's canopy. No record was found indicating that this pilot report (PIREP) was relayed to the incident flight crew or other aircraft operating near the incident airport. Both airports are under the control of the same approach control facility. The meteorological conditions at the time of the accident were conducive to a very light freezing or frozen precipitation environment very close to or at the surface. Therefore, it is likely that the airplane encountered significant in-flight icing conditions during the approach and landing that exceeded the capabilities of the airplane's anti-ice systems. In addition, if the pilots had been made aware of the severe icing PIREP from the nearby airport, they likely would have had other options available for landing. The Federal Aviation Administration has indicated that it will form a PIREP working group to address issues associated with the dissemination of PIREPs.

Probable cause

The flightcrew's loss of visual reference to the runway after encountering severe in-flight icing conditions, which resulted in a loss of control while landing and exceedence of the capabilities of the airplane's windscreen anti-ice systems. Contributing to this incident was the failure of the approach controller to relay a pilot report of severe icing conditions near the route of flight to the incident flight crew.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC12IA024
Event ID
20120306X11830
Case number
ANC12IA024
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2012-03-06.
  • API snapshot SHA-256: c8547620de7a166533f7a3fa97d4fce4faf4579d3089cf388272bd42f7e976bc; retrieved 2026-09-15T17:23:09.530Z.