CEN10MA088 · Gates Learjet CORP. 35A
Royal Air Freight Gates Learjet CORP. 35A · Accident: loss of control in flight on approach
From Oakland County International Airport (PTK) to Prospect Heights, IL
Event
- NTSB case
- CEN10MA088
- 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
- 2 · 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
Gates Learjet CORP. 35A
- Aircraft type
- Learjet 35
- 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
- N720RA
- Operator
- Royal Air Freight
- Onboard fatalities
- Unknown
- Route
- From Oakland County International Airport (PTK), Pontiac, MITo Prospect Heights, IL
- 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 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
- Loss of control in flight
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight was scheduled to pick up cargo at the destination airport and then deliver it to another location. During the descent and 14 minutes before the accident, the airplane encountered a layer of moderate rime ice. The captain, who was the pilot flying, and the first officer, who was the monitoring pilot, made multiple statements which were consistent with their awareness and presence of airframe icing. After obtaining visual flight rules conditions, the flight crew canceled the instrument flight rules clearance and continued with a right, circling approach to the runway. While turning into the base leg of the traffic pattern, and 45 seconds prior to the accident, the captain called for full flaps and the engine power levers were adjusted several times between 50 and 95 percent. In addition, the captain inquired about the autopilot and fuel balance. In response, the first officer stated that he did not think that the spoilerons were working. Shortly thereafter, the first officer gave the command to add full engine power and the airplane impacted terrain.
There was no evidence of flight crew impairment or fatigue in the final 30 minutes of the flight. The cockpit voice recorder showed multiple instances during the flight in which the airplane was below 10,000 feet mean sea level that the crew was engaged in discussions that were not consistent with a sterile cockpit environment, for example a lengthy discussion about Class B airspeeds, which may have led to a relaxed and casual cockpit atmosphere. In addition, the flight crew appears to have conducted checklists in a generally informal manner. As the flight was conducted by a Part 135 operator, it would be expected that both pilots were versed with the importance of sterile cockpit rules and the importance of adhering to procedures, including demonstrating checklist discipline.
For approximately the last 24 seconds of flight, both pilots were likely focusing their attention on activities to identify and understand the reason for the airplane's roll handling difficulties, as noted by the captain's comment related to the fuel balance. These events, culminating in the first officer's urgent command to add full power, suggested that neither pilot detected the airplane's decaying energy state before it reached a critical level for the conditions it encountered.
Light bulb filament examination revealed that aileron augmentation system and stall warning lights illuminated in the cockpit. No mechanical anomalies were found to substantiate a failure in the aileron augmentation system. No additional mechanical or system anomalies were noted with the airplane. A performance study, limited by available data, could not confirm the airplane's movements relative to an aileron augmentation system or spoileron problem. The level of airframe icing and its possible effect on the airplane at the time of the accident could not be determined.
Probable cause
A loss of control for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10MA088
- Event ID
- 20100105X11839
- Case number
- CEN10MA088
- 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: 49dab654bc4f98e9e3b394ff7f6712da3d766d339b415303259318f23465da9e; retrieved 2026-09-13T20:36:10.218Z.