MIA97LA008 · Cessna 21OK
Cessna 21OK and Beech 23 · Accident: midair collision on approach
Event
- NTSB case
- MIA97LA008
- 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 21OK
- Aircraft type
- Cessna 21
- 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
- N81SC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From X16To Albert Whitted Airport (SPG), St. Petersburg, FL
- 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
- Approach · VFR pattern downwind
- 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
Aircraft 2 · Beech 23
- Aircraft type
- Beechcraft 23
- 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
- N4021T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lakeland Linder International Airport (LAL), Lakeland, FLTo X16
- 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
- Approach · VFR pattern downwind
- 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, inadequate
- Pilot of other aircraft › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The Cessna 210, N81SC, was planning on departing the traffic pattern on the downwind leg and reportedly announced his takeoff, crosswind and downwind turns. The Beech 23, N4021T, was inbound from the north and announced his intention of a 'long' 2 mile downwind, which was reportedly heard by an employee at the airport. The Cessna was just completing the turn to downwind at 900 feet when the collision occurred. The pilots of both airplanes were able to land at the airport. A witness observed the collision and reported that it occurred about 1/4 mile north and 1/3 mile west of the departure end of runway 36. A component from the Cessna was found in a field located about 1 nautical mile and 322 degrees from the departure end of the runway. The AIM recommends that aircraft depart the traffic pattern either on the upwind leg or turn 45 degrees to the left while in the upwind leg. The recommended downwind entry is at a 45 degree angle abeam the midpoint of the downwind leg.
Probable cause
The failure of the pilots of both airplanes to see and avoid each other. Contributing to the accident was the improper planning/decision of the pilot of the Cessna 210 to depart the traffic pattern on the downwind leg rather than on the upwind leg as recommended in the AIM, and the improper planning/decision of the pilot of the Beech 23 to enter a 2-mile downwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA97LA008
- Event ID
- 20001208X06948
- Case number
- MIA97LA008
- 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: 5be92be92dbbae3b7e18961e128df6cdd1ff90588c5281bf4ee528c7b5fb235b; retrieved 2026-09-21T21:33:29.646Z.