Gates Lear Jet 36 N26FN
9 September 2022 · San Diego, California, United States · Minor injuries
Summary
On 9 September 2022 at about 20:14 local time, a Gates Lear Jet 36 registered N26FN, operated by Strategic Airborne Operations, was involved in an accident near San Diego, California, United States. 2 people were on board and 2 had minor injuries. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 20:14
- Classification
- Accident
- Location
- San Diego, California, United States
- Nearest airport
- North Island Nas /Halsey Fld/ (NZY)
- Coordinates
- 32.6982, -117.2131
- Aircraft
- Gates Lear Jet 36
- Registration
- N26FN
- Category
- Airplane
- Year built
- 1975
- Engines
- 2
- Operator
- Strategic Airborne Operations
- Operating rule
- Public Use
- Purpose of flight
- Other Work Use
- Phase of flight
- Not recorded
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR22LA344
People
2 people had minor injuries.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 0 | 0 | 2 | 0 |
Probable cause
The flight crew’s fast landing on a wet runway, which resulted in the airplane hydroplaning during the landing roll and subsequently overrunning the runway.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The flight crew was supporting a United States Navy (USN) training mission and ended the flight early due to icing conditions. The flight crew calculated a landing reference speed (Vref) of 140 knots (kts) indicated airspeed (KIAS) and landing distance required of 4,200 ft for a wet runway and a flap setting of 20°. Due to underwing-mounted external storage, the landing flaps were limited to a maximum extension of 20°. The flight crew configured the airplane with 20° flaps and reported that the airplane touched down at 140 kts. Although the runway was 8,001 ft long, an arresting cable was located 1,701 ft from the runway threshold, resulting in a runway distance available of about 6,300 ft. After landing, the second in command (SIC) reported that the pilot-in-command (PIC) deployed the spoilers and brakes, then announced that the airplane was not slowing down. The PIC stated that the airplane did not decelerate normally, that the brake anti-skid system was active, and that the airplane seemed to be hydroplaning. He cycled the brakes, which had no effect. The airplane subsequently overran the departure end of the runway, breached an ocean sea wall and came to rest in a nose-down attitude on a sandbar. The airport weather observation system recorded that 0.06 inches of liquid equivalent precipitation fell between 18 and 9 minutes before the accident. In the 4 hours before the accident, the airport received 0.31 inches of liquid equivalent precipitation. A landing performance study conducted by the airplane manufacturer modeled a variety of landing scenarios considered during the investigation. The modeling used factual information provided by the investigation, including ADS-B data, as well as manufacturer-provided airplane performance data specific to the airplane. The study considered the effect on landing distance of both a wet and dry runway, a contaminated runway, both full and intermittent hydroplaning, a localized tailwind (which was not present in the weather data), and an inboard brake failure. The study showed that the most likely scenario, based on the available data, was that the airplane touched down with a ground speed well in excess of the 140 kts Vref speed reported by the crew, and that subsequent to the touchdown encountered full hydroplaning at speeds above 104 kts. The airplane sat overnight on the sandbar and was submerged in saltwater before the airplane was recovered. As a result, the airplane’s braking system could not be functionally tested. However, the physical evidence from the brakes as found postaccident, combined with the results of the landing distance modeling, did not indicate that a brake failure occurred. Similarly, ADS-B data did not support the presence of a localized tailwind when such a landing was modeled in the study. Thus, it’s likely that the flight crew landed too fast and then encountered hydroplaning during the landing roll as a result of a recent heavy rain shower, which diminished the calculated stopping distance.
Quoted verbatim from the NTSB record.
Other Gates Lear Jet 36 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 30 Nov 2022 | Gates Lear Jet 36 | Newport News, Virginia, United States | Aery Aviation | No injuries | - |
| 10 May 2023 | Gates Lear Jet 36A | San Clemente Island, California, United States | Phoenix Air Group Inc | Fatal | 3 |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 2 Mar 2022 | Cessna 182D | Desert Camp, California, United States | Cloudstreet Flying Services | No injuries | - |
| 4 Sep 2022 | Bell 407 | Mount Baldy, California, United States | Air Methods Corp | Serious injuries | - |
| 16 Apr 2022 | Stoddard Hamilton GLASAIR SUPER II | Oxnard, California, United States | - | No injuries | - |
| 28 Dec 2022 | Embraer Executive EMB-505 | Hawthorne, California, United States | Solairus Aviation | No injuries | - |
| 10 Jun 2022 | Mooney M20K | Camarillo, California, United States | - | Fatal | 1 |
| 23 Jul 2022 | North American T-28B | Fallbrook, California, United States | Mach One Air Charters Inc | Fatal | 1 |