CHI94LA178 · Cessna 150L
Cessna 150L and Cessna 172N · Accident: collision between aircraft (not in flight) during takeoff
Event
- NTSB case
- CHI94LA178
- 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
- 1 · 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 150L
- Aircraft type
- Cessna 150
- 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
- N153KA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Richmond Municipal Airport (RID), INTo 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
- Takeoff
- 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
- Collision between aircraft (not in flight)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Aircraft 2 · Cessna 172N
- 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
- N733DW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dayton-Phillipsburg Airport (3I7), Phillipsburg, OHTo Richmond Municipal Airport (RID), IN
- 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
- Collision between aircraft (not in flight)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Dual student › Visual lookout, inadequate
- Pilot in command(cfi) › Visual lookout, inadequate
- Pilot of other aircraft › Visual lookout, inadequate
Approximate · Estimated position: the centre of Richmond, IN, the place the record names. Not the accident site.
NTSB narrative
A STUDENT & INSTRUCTOR (CFI) IN CESSNA 150, N153KA, WERE PERFORMING A TOUCH-&-GO ON RUNWAY 33, WHILE A STUDENT & CFI IN A CESSNA 172, N733DW, WERE PERFORMING A TOUCH-&-GO ON RUNWAY 24. THE 2 AIRPLANES COLLIDED AT THE INTERSECTION OF THE RUNWAYS. THE CFI OF THE CESSNA 150 SAID THEY MADE ADVISORY CALLS ON THE UNICOM FREQUENCY BEFORE ENTERING THE TRAFFIC & ON ALL LEGS OF THE TRAFFIC PATTERNS. THE CESSNA 150 PILOTS INITIALLY ENTERED TRAFFIC FOR RUNWAY 24, THEN CHANGED TO RUNWAY 33. THE CFI OF THE CESSNA 172 REPORTED THEY WERE PRACTICING USAGE OF THE VOR, WHILE EN ROUTE TO THE AIRPORT & THAT RADIO TRANSMISSION(S) WERE MADE ON THE UNICOM FREQUENCY BEFORE ENTERING A STRAIGHT-IN APPROACH TO RUNWAY 24. ALSO, HE STATED THAT THE STUDENT (IN THE CESSNA 172) MADE THE LANDING & THAT THE AIRPLANE FLOATED & TOUCHED DOWN LONG. THE CFI'S IN BOTH AIRPLANES SAW THE OTHER PLANE JUST BEFORE IMPACT. THE CFI IN THE CESSNA 150 ROTATED THE AIRCRAFT IN AN ATTEMPT TO CLIMB, BUT WAS UNABLE TO AVOID A COLLISION.
Probable cause
INADEQUATE VISUAL LOOKOUT BY THE PILOTS OF BOTH AIRPLANES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI94LA178
- Event ID
- 20001206X01256
- Case number
- CHI94LA178
- 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: ade88b14067281a09b02c9d3969879f1e0b81f734a3caa8424cafea79fe4db02; retrieved 2026-09-21T00:08:46.893Z.