MIA03LA038 · North American AT-6A
North American AT-6A and Cessna 172K · Accident: on ground/water collision with object while taxiing
Event
- NTSB case
- MIA03LA038
- 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
- Unknown
- 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 · North American AT-6A
- Aircraft type
- North American AT-6
- 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
- N57318
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Melbourne Orlando International Airport (MLB), Melbourne, FLTo Melbourne Orlando International Airport (MLB)
- 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
- Taxi · from runway
- 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
Aircraft 2 · Cessna 172K
- 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
- N522F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Daytona Beach International Airport (DAB), Daytona Beach, FLTo Melbourne Orlando International Airport (MLB), Melbourne, 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
- Taxi · from runway
- 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, not maintained
- Pilot of other aircraft › Visual lookout, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot of N57318, a North American AT6A, said that he had landed on runway 27L, and had been told to hold short of runway 27R. He said that the FAA Air Traffic Control Tower controller told the pilot of the N522F, a Cessna 172K, to taxi to the ramp, and that his airplane has restricted visibility and that suddenly and unexpectedly the Cessna appeared on the taxiway ahead of him and he collided with it. The pilot of the North American stated that there were no mechanical failures or malfunctions to his airplane or any of its systems. The pilot of the Cessna stated that after landing on runway 27R, he turned on taxiway Q, crossed the hold short line, and came to a complete stop in order to complete the after landing checklist, and the North American impacted the tail of his airplane. The FAA Air Traffic Controller stated that the North American landed on runway 27L and turned off at runway Q, and the pilot of the North American was instructed to hold short of runway 27R. He said the Cessna landed on runway 27R and after landing was instructed to turn right at "Q" and taxi to parking. When the Cessna had turned off the runway, he said he then instructed the North American to taxi to cross runway 27R and taxi to parking, and within a few moments the collision occurred. One of the witnesses stated that she saw the North American run into the back of the Cessna, and further stated that she did not see the North American engaged in any "S-turn" maneuvers as it was being taxied.
Probable cause
The failure of the pilot of the North American AT6A, N57318 to maintain a proper visual lookout while taxiing, which resulted in him impacting the rear of the Cessna 172K, N522F.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03LA038
- Event ID
- 20030110X00047
- Case number
- MIA03LA038
- 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, coordinates. 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: 80550026c97d441be5f783c6c952a604a5e7dad9d4725f2c21c7b6756a2d57ce; retrieved 2026-09-22T09:43:06.762Z.