FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI93LA214 · Cessna 172D

18 Jun 1993 · Galesburg, IL, United States

S & A Aviation Cessna 172D and Perceptive Enterprises Piper PA-32-300 · Accident: on ground/water collision with object during landing

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

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

Aircraft 1 · Cessna 172D

Aircraft type
Cessna 172
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
N2632U
Onboard fatalities
Unknown
Route
From 7C2 · Mediapolis, IATo not recorded
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 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 · landing roll
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
Substantial

Aircraft 2 · Piper PA-32-300

Aircraft type
Piper PA-32
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
N251NW
Onboard fatalities
Unknown
Route
From Galesburg Regional HW Timmons Airport (GBG)To Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP), Minneapolis, MN
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 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
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
Substantial

Cause areas

  • Pilot in command › Visual lookout, inadequate
  • Pilot of other aircraft › Visual lookout, inadequate

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

NTSB narrative

N251NW WAS DEPARTING ON RUNWAY 2 AND N2632U WAS LANDING ON RUNWAY 10. THE AIRPLANES COLLIDED AT THE INTERSECTION OF THE TWO RUNWAYS. A WEATHER OBSERVATION MADE FIFTEEN MINUTES AFTER THE ACCIDENT INDICATED AN OVERCAST CLOUD LAYER AT 2000 FEET, 3 MILES VISIBILITY, AND WINDS OUT OF 070 DEGREES AT 3 KNOTS. BOTH PILOTS STATED THEY COMMUNICATED THEIR INTENTIONS ON THE UNICOM FREQUENCY. AIRPORT PERSONNEL ADVISED THEY HEARD TRANSMISSIONS FROM THE AIRPLANE INBOUND FOR LANDING. BOTH PILOTS STATED THEY DID NOT SEE THE OTHER AIRPLANE UNTIL JUST PRIOR TO IMPACT. THE PILOT OF N251NW REPORTED THAT HE CHECKED THE GAUGES OF HIS AIRCRAFT DURING THE TAKEOFF ROLL AFTER HAVING HAD A PREVIOUS MAGNETO TIMING PROBLEM.

Probable cause

THE DEPARTING PILOT'S (N251NW) INADEQUATE VISUAL LOOKOUT WHILE OPERATING IN VFR CONDITIONS AT AN UNCONTROLLED AIRPORT. FACTORS RELATED TO THE ACCIDENT WERE: THE DEPARTING PILOT'S DIVERTED ATTENTION, AND THE ARRIVING PILOT'S (N2632U) INADEQUATE VISUAL LOOKOUT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI93LA214
Event ID
20001211X12574
Case number
CHI93LA214
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: 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: 67f29f7ce99be8d7973cb3eaf2faaf55593efe1c69c2433d452ad5eb9288683c; retrieved 2026-09-21T22:55:08.937Z.