GAA16LA086 · Hawker Beechcraft Corp 390
Hawker Beechcraft Corp 390 · Accident: abnormal runway contact during landing
From Monmouth Executive Airport (BLM) to Chicago Executive Airport (PWK)
Event
- NTSB case
- GAA16LA086
- 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
Hawker Beechcraft Corp 390
- Aircraft type
- Hawker Beechcraft 390
- 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
- N50VM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Monmouth Executive Airport (BLM), BELMAR/FARMINGDALE, NJTo Chicago Executive Airport (PWK), CHICAGO/PROSPECT HEIGHTS/WHEELING, IL
- Aircraft age
- About 7 years (built 2008)
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The first pilot, who was the owner of the light jet and had recently received a type rating in the airplane, was acting as pilot-in-command for the flight and was seated in the left seat. A second pilot, who was also type-rated and experienced in the airplane make and model and was accompanying the first pilot as a mentor, was seated in the right seat and handled radio communications throughout the flight. As they neared the destination airport for an approach to runway 16, the pilots received the most recent weather information, which included wind from 250 degrees at 16 knots (kts) with gusts to 29 kts. Shortly thereafter, another pilot on the frequency reported wind gusts of 50 kts upon landing. The first pilot expressed concern about landing in such windy conditions, but the second pilot encouraged him to continue. About 45 ft above the runway, the airplane experienced a strong gust of wind; the left wing impacted the ground, and the second pilot initiated a go-around. The second pilot then reconfigured the airplane for a landing on runway 30; the aural "wind shear" warning was sounding throughout the approach. Upon touchdown, the airplane's right main landing gear exited the runway surface and impacted the raised curb between the grass and taxiway surface. Both pilots reported that there were no preaccident airplane anomalies that would have precluded normal operation.
The maximum demonstrated crosswind component of the airplane was 25 kts. Given the reported wind conditions about the time of the accident, the crosswind component was at least 16 to 29 kts during the first landing attempt, and may have been greater based on the pilot report of gusts. Thus, the pilots should not have attempted the landing, because the gusts had the potential to exceed the airplane's maximum demonstrated crosswind component.
Probable cause
The pilots' decision to conduct an approach and landing in gusting wind conditions, and their failure to maintain control of the airplane during the first approach, which resulted in a wing strike.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16LA086
- Event ID
- 20151222X24312
- Case number
- GAA16LA086
- 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: 10e3e77fceaff67cd5181a36b20929f8eecdd8c17b500aefe5894bdafb9dac7f; retrieved 2026-09-16T03:02:49.146Z.