ERA12IA166 · Gulfstream G150
Chattem Gulfstream G150 · Incident: landing area overshoot
From Pocono Mountains Municipal Airport (MPO) to Baltimore/Washington International Thurgood Marshall Airport (BWI)
Event
- NTSB case
- ERA12IA166
- 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
- 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
Gulfstream G150
- Aircraft type
- Gulfstream G150
- 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
- N272CB
- Operator
- Chattem
- Onboard fatalities
- Unknown
- Route
- From Pocono Mountains Municipal Airport (MPO), Mount Pocono, PATo Baltimore/Washington International Thurgood Marshall Airport (BWI), Baltimore, MD
- 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
- 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
- Landing area overshoot
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was approaching the destination airport in night visual meteorological conditions. The pilot-in-command (PIC) was the pilot flying and was not familiar with the destination airport. The second-in-command (SIC) was the pilot monitoring and was familiar with the destination airport. While the airplane was at 2,000 feet mean sea level, about 10 miles from the airport, the PIC did not see the airport; however, the SIC observed the airport beacon, but not runway 33R. The controller then offered either a clearance for a visual approach to runway 33R or a vector for the runway 33R instrument landing system (ILS) approach. The PIC indicated to the SIC that he wanted the ILS; however, the SIC stated that he saw runway 33R and asked the PIC if he saw it, to which he replied no. The SIC then told the controller that they had the runway in sight. The PIC subsequently stated to the SIC that he saw runway 33R, but he confused it with runway 28.
About 2 minutes later, with the SIC assisting, the PIC visually acquired the correct runway. At that time, the airplane was about 6 miles from the runway, at 1,400 feet msl. The airplane made a left turn, followed by a right turn, which positioned it from a final approach to runway 28, to a final approach to runway 33R. The airplane was lined-up for runway 33R about 4 miles from the runway threshold, at 1,000 feet and 145 knots groundspeed. While on short final approach, about 300 feet agl, the airspeed went below the landing reference speed (Vref) by about 3 to 5 knots. The SIC responded by emphasizing "below Vref" two times, followed by "power" four times. The PIC added power and the airplane's speed went above Vref by about 10 knots.
The airplane touched down about halfway down the 5,000 foot-long runway, about 140 knots groundspeed with an approximate 5-knot tailwind. Although the flight crew did not believe the thrust reversers activated, non-volatile memory (NVM) of the engine controls revealed that they deployed for 13 seconds; however, the airplane still traveled off the end of the runway and came to rest in mud about 200 feet from the departure end. Examination of the airplane and its other NVM did not reveal any preimpact mechanical malfunctions. The flight crew did not report any additional anomalies, including the breaking system, and 226 feet of pulsing skid marks were identified near the departure end of the runway.
Probable cause
The pilot-in-command's failure to obtain the proper touchdown point or landing reference speed and failure to initiate a go-around when it became evident that the airplane was landing long and fast. Contributing to the incident was a lack of effective flight crew coordination and communication.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12IA166
- Event ID
- 20120131X75454
- Case number
- ERA12IA166
- 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: 0ce30d84c4ff04f066c4beba5cd0be86928108eda0aad5f5b52a3cf427fdbfb0; retrieved 2026-09-15T17:08:51.819Z.