FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19TA133 · Cessna 650

14 Mar 2019 · Sanford, FL, United States

Rp Sales And Leasing Cessna 650 · Accident while taxiing

From Yeager Airport (CRW) to Orlando Sanford International Airport (SFB)

Report a problem

Event

NTSB case
ERA19TA133
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

Cessna 650

Aircraft type
Cessna 650
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
N220CM
Onboard fatalities
Unknown
Route
From Yeager Airport (CRW), Charleston, WVTo Orlando Sanford International Airport (SFB), Sanford, FL
Aircraft age
About 31 years (built 1988)
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
Taxi · from runway
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
Miscellaneous/other
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 › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot stated that after landing the airplane at night, the taxiway that he normally used was occupied, so he taxied toward the ramp via an alternate taxiway. As he approached the ramp, there were four or five airplanes on the ramp, and the pilot asked the copilot if the area was clear on the right side. The pilot was referring to the ground path, but the copilot thought he was referring to the other airplanes. When the copilot replied that they were clear, the pilot turned right. The airplane then exited the taxiway onto grass and the nosewheel struck concrete, which resulted in substantial damage to the fuselage structure above the nose landing gear. The pilot reported that there were no preimpact mechanical malfunctions with the airplane.

Probable cause

The pilot's failure to keep the airplane on the taxiway while taxiing at night. Contributing to the accident was a miscommunication between the flight crewmembers about the position of the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19TA133
Event ID
20190322X14036
Case number
ERA19TA133
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: 81f85094bb5d64f7acccfcdb3e8f454e787f42e3c5eb30f0f958d01fdc6fc3ab; retrieved 2026-09-16T08:40:52.231Z.