FTW00FA083 · Cessna 182M
Cessna 182M and Cessna 208B · Accident: midair collision while maneuvering
Event
- NTSB case
- FTW00FA083
- 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
- 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
Aircraft 1 · Cessna 182M
- Aircraft type
- Cessna 182
- 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
- N91994
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Neosho Hugh Robinson Airport (EOS), Neosho, MOTo Mc Alester Regional Airport (MLC)
- 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
- Maneuvering
- 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
- Midair collision
- 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 208B
- Aircraft type
- Cessna 208
- 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
- N9505B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Mc Alester Regional Airport (MLC)To Stan Stamper Municipal Airport (HHW), Hugo, OK
- 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
- Maneuvering
- 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
- Midair collision
- 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, not maintained
- Pilot of other aircraft › Visual lookout, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the Cessna 208 reported that as he was taxiing for takeoff, he heard the pilot of the Cessna 182 make a radio call on the non-towered airport's common traffic advisory frequency asking for an airport advisory. The pilot of the Cessna 208 responded to the Cessna 182 pilot, stating that the winds were from 020 degrees at 15 knots gusting to 23 knots, and he was going to depart from runway 01. The Cessna 208 pilot reported that he did not hear any further radio calls from the Cessna 182. Upon reaching runway 01, the pilot of the Cessna 208 determined that there 'were no other planes in the pattern and nobody on the radio' and departed. He made his takeoff, climbed straight-out until the airplane reached 500 feet agl and then turned the airplane left onto the crosswind leg. He flew a normal left hand traffic pattern and leveled the airplane at 1,000 feet agl. He flew the downwind leg until the airplane was 'past mid-field,' and prior to turning left to a heading of 160 degrees on course for Hugo, he looked to the left to clear the area and 'was surprised to see an object coming closer.' He determined that the object 'was a high-wing Cessna coming from slightly above and behind [his] left wing-tip,' which was descending toward his cockpit. He reduced power, rolled right and nosed down. He stated that the Cessna 182 'turned left as in a normal x-wind to downwind turn [and] did not take evasive action.' He further stated that the Cessna 182 'flew over [his] cockpit and the 2 planes hit in a glancing blow.' Following the collision, the Cessna 182 impacted the ground and the Cessna 208 returned and landed on runway 01. The Cessna 182 was destroyed by impact forces and fire and no evidence of contact with the Cessna 208 was identified. Damage to the Cessna 208 was confined to the outboard portion of the left wing and left aileron, which were bent upwards approximately 60 degrees, 5 feet inboard from the wing-tip.
Probable cause
The failure of both pilots to maintain visual lookout while maneuvering in the traffic pattern.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00FA083
- Event ID
- 20001212X20487
- Case number
- FTW00FA083
- 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: a375002fe8eb8d2bb1bbf4c0401dc91891a83a0dfb6bdf08da6dde36cb290b1a; retrieved 2026-09-18T13:13:17.937Z.