International Jet Charter Gates Learjet 35A accident
Gates Learjet 35A · Accident: in flight collision with terrain/water on approach
From Atlantic City International Airport (ACY) to Groton New London Airport (GON)
Event
- NTSB case
- NYC06FA137
- 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
- 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
Gates Learjet 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
- N182K
- Operator
- International Jet Charter
- Onboard fatalities
- Unknown
- Route
- From Atlantic City International Airport (ACY), Atlantic CityTo Groton New London Airport (GON), Groton, CT
- 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
- Approach · IFR final approach
- 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
- In flight collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Flightcrew › Diverted attention
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The crew briefed the Instrument Landing System approach, including the missed approach procedures. Weather at the time included a 100-foot broken cloud layer, and at the airport, 2 miles visibility. The approach was flown over water, and at the accident location, there was dense fog. Two smaller airplanes had successfully completed the approach prior to the accident airplane. The captain flew the approach and the first officer made 100-foot callouts during the final descent, until 200 feet above the decision height. At that point, the captain asked the first officer if he saw anything. The first officer reported "ground contact," then noted "decision height." The captain immediately reported "I got the lights" which the first officer confirmed. The captain reduced the power to flight idle. Approximately 4 seconds later, the captain attempted to increase power. However, the engines did not have time to respond before the airplane descended into the water and impacted a series of approach light stanchions, commencing about 2,000 feet from the runway. Neither crew member continued to call out altitudes after seeing the approach lights, and the captain descended the airplane below the decision height before having the requisite descent criteria. The absence of ground references could have been conducive to a featureless terrain illusion in which the captain would have believed that the airplane was at a higher altitude than it actually was. There were no mechanical anomalies which would have precluded normal airplane operation.
Probable cause
The crew's failure to properly monitor the airplane's altitude, which resulted in the captain's inadvertent descent of the airplane into water. Contributing to the accident were the foggy weather conditions, and the captain's decision to descend below the decision height without sufficient visual cues.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06FA137
- Event ID
- 20060622X00800
- Case number
- NYC06FA137
- 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, 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: d1d8f07cc16d44e8c6c9c91016bce0301d5c49bbe5d32edad56930834f2e3dd5; retrieved 2026-09-18T12:56:57.984Z.