FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Sparta Aviation Service Cessna 402B incident

24 Sept 1999 · Chicago, IL, United States

Cessna 402B · Incident: on ground/water collision with object during takeoff

From Chicago Midway International Airport (MDW) to Gerald R. Ford International Airport (GRR)

Report a problem

Event

NTSB case
CHI99IA351
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
Incident
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
Charter & commuter
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 402B

Aircraft type
Cessna 402
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
N6362X
Onboard fatalities
Unknown
Route
From Chicago Midway International Airport (MDW), ILTo Gerald R. Ford International Airport (GRR), Grand Rapids, MI
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 135: Air Taxi & Commuter
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
Takeoff · roll/run
First occurrenceThe 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
On ground/water collision with object
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Pilot in command › Clearance, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane struck airport lighting during an aborted takeoff. The pilot said, "I followed the taxi line until I found a white line and lined up on it. I applied partial power, ...when I noticed what I thought was a box on the runway (all I could discern was a black cube)." He said, "...I heard a WHUMP, but felt no yaw or any adverse affect on the airplane." He "...heard what seemed like a buzz." He aborted the takeoff, taxied to the parking ramp, and found propeller damage. A runway inspection revealed a damaged directional sign and runway light on runway 31C's northeast shoulder prior to the runway's displaced threshold. An investigation revealed that near the foxtrot taxiway on runway 31C two taxiway centerline markings branched out from and were located north of the taxiway's lead-in line for runway 31C's centerline. These two taxiway centerline markings were located on the runway's approach side of the displaced threshold bar for runway 31C and these taxiway centerline markings did cross the solid white northeast runway side stripe for runway 31C. Runway 31C's shoulder, at the incident site, was found without shoulder markings. Advisory Circular 150/5340-1H states, "Runway shoulder markings are used ... where pilots have experienced problems identifying the runway from the shoulder thereby creating a need to delineate the shoulder as unusable pavement."

Probable cause

THE FAILURE OF THE PILOT IN COMMAND TO MAINTAIN CLEARANCE WITH GROUND OBSTRUCTIONS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI99IA351
Event ID
20001212X19705
Case number
CHI99IA351
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1999-09-25.
  • API snapshot SHA-256: 4f5e7f3dc279a1721ed918a231284ff7bc6a6c5be3b09bedf1ad32c04f6c364a; retrieved 2026-09-18T16:52:38.346Z.