ERA20CA120 · Learjet 35 A
East Coast Jets Learjet 35 A · Accident: abnormal runway contact on approach
From Lehigh Valley International Airport (ABE) to Altoona Blair County Airport (AOO)
Event
- NTSB case
- ERA20CA120
- 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
- Instrument Meteorological Cond
Learjet 35 A
- 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
- N721EC
- Operator
- East Coast Jets
- Onboard fatalities
- Unknown
- Route
- From Lehigh Valley International Airport (ABE), Allentown, PATo Altoona Blair County Airport (AOO), Altoona, PA
- Aircraft age
- About 40 years (built 1980)
- 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
- Approach · VFR go-around
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight crew reported that, after an instrument landing system approach and during the landing flare, the airplane encountered a strong wind gust that pushed the airplane toward the edge of the runway, so they initiated a go-around. During the go-around, the left-wing tip tank struck the runway. The flight crew diverted to another airport where the weather conditions were more favorable, and after landing, examination of the airplane revealed that the left wing had sustained substantial damage. The calculated crosswind component was 18 knots at the time of landing. According to the Airplane Flight Manual, the maximum demonstrated crosswind component was 24.7 knots.
Probable cause
The pilot flying's improper lateral bank control during a go-around in gusting wind conditions, which resulted in the left-wing tip tank striking the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA120
- Event ID
- 20200229X74252
- Case number
- ERA20CA120
- 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: 803a061fbc03892a15b6c0fcd868a3491c6c14e113a74c422141932d3a4f1b47; retrieved 2026-09-16T11:13:15.534Z.