ERA11CA280 · Bombardier BD700 1A10
Global Flight Bombardier BD700 1A10 · Accident: abnormal runway contact during landing
From PBI · West Palm Beach, FL to Teterboro Airport (TEB)
Event
- NTSB case
- ERA11CA280
- 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
- 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
Bombardier BD700 1A10
- Aircraft type
- Bombardier BD700
- 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
- N113CS
- Operator
- Global Flight
- Onboard fatalities
- Unknown
- Route
- From PBI · West Palm Beach, FLTo Teterboro Airport (TEB), Teterboro, NJ
- 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
- Abnormal runway contact
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot flying, the airplane was vectored onto the final approach course and the pilot not flying had configured the airplane to land. The pilot not flying reported that during the approach the airspeed was fluctuating by 20 knots. As the pilot flying flared, the airplane encountered a gust of wind, rolled left, and full opposite aileron was applied; however, the left wing impacted the runway. The pilot landed, slowed to taxi speed, and exited the runway. Postaccident examination of the airplane revealed substantial damage to the left outboard forward wing spar. The wind, approximately 5 minutes prior to the accident, was recorded as 310 degrees at 20 knots, gusting to 33 knots. A peak wind was recorded about the time of the accident as 300 degrees at 33 knots.
Probable cause
The pilot's loss of aircraft control during landing in gusty wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA280
- Event ID
- 20110504X12246
- Case number
- ERA11CA280
- 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: 1d6c4fa3ea00a47bc93d999b29569bcdc3366a1ac42c26c6df9efa28a23c6240; retrieved 2026-09-15T16:07:36.639Z.