ERA22LA190 · Textron Aviation Inc 525B
Textron Aviation Inc 525B · Accident: landing area overshoot
From Saint Paul Downtown Holman Field (STP) to Essex County Airport (CDW)
Event
- NTSB case
- ERA22LA190
- 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
- 0
- 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
Textron Aviation Inc 525B
- Aircraft type
- Cessna 525
- 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
- N225SC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Saint Paul Downtown Holman Field (STP), St Paul, MNTo Essex County Airport (CDW), Caldwell, NJ
- Aircraft age
- About 2 years (built 2020)
- 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
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot-in-command (PIC) of the business jet described that at the conclusion of the flight the second-in-command (SIC) would conduct the landing. The SIC briefed the approach and the PIC agreed. The tower cleared the airplane for the visual approach to runway 22 (4,552-ft-long), noting winds were 300° at 18 knots, gusting to 26 knots. The PIC told the SIC that if he did not feel comfortable with the approach to landing, he should voice his concern, and initiate a go-around or transfer control of the airplane to the PIC. The PIC also briefed the procedure for taking control of the airplane should any unsafe conditions be observed. The PIC further described that after turning final, the landing checklist was completed, and the airplane was established on a stabilized approach. The SIC noted that he would fly at a slightly higher speed due to varying winds and gusts. Just before touchdown, the airplane “encountered a gust of wind that resulted in a ground effect float.” The airplane then touched down “at Ref speed” and on what the PIC perceived to be the first third of the runway. Due to the float and wind gust upon touchdown, the PIC called for the controls with the intent to initiate a go-around or to bring the airplane to a stop. The PIC then decided not to commence a go-around due to the limited amount of remaining runway available, low airspeed, and time to initiate takeoff power. The PIC realized that the airplane would not come to a stop on the remaining runway, even with maximum braking applied, and the airplane overran the runway and came to a stop in a brook beyond the departure end. The forward portion of the fuselage was substantially damaged during the runway excursion. The PIC reported that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation. Review of airport surveillance camera footage showed that the airplane touched down beyond the midpoint of the runway.
Probable cause
The flight crew’s failure to attain a proper touchdown point during landing, which resulted in an overrun of the runway and collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA190
- Event ID
- 20220418104951
- Case number
- ERA22LA190
- 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, cause areas. 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: 50b444b8c8fc0cfdf99f8632374a4938e48cf526f3edf86af91e30aa4a0482a8; retrieved 2026-09-16T15:08:11.056Z.