NYC07MA162 · Cessna 310R
National Association for Stock Car Auto Racing Cessna 310R · Accident: fire en route
From Daytona Beach International Airport (DAB) to Lakeland Linder International Airport (LAL)
Event
- NTSB case
- NYC07MA162
- 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
- 5 · all aircraft and ground
- Ground fatalities
- 3
- 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
Cessna 310R
- Aircraft type
- Cessna 310
- 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
- N501N
- Onboard fatalities
- Unknown
- Route
- From Daytona Beach International Airport (DAB), Daytona Beach, FLTo Lakeland Linder International Airport (LAL), Lakeland, 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
- En route · cruise
- 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
- Fire
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Company maintenance personnel › Improper decision
- Company/operator management › Improper decision
- Flightcrew › Planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The Safety Board's full report is available at http://www.ntsb.gov/publictn/A_Acc1.htm. The Aircraft Accident Report number is NTSB/AAR-09-01.
On July 10, 2007, about 0835 eastern daylight time, a Cessna Aircraft Company 310R, N501N, part of the fleet operated by the National Association for Stock Car Auto Racing (NASCAR) corporate aviation division, crashed while performing an emergency diversion to Orlando Sanford International Airport, Orlando, Florida. The two pilots on board the airplane (a commercial pilot and an airline transport pilot) and three people on the ground were killed. Four people on the ground received serious injuries. The airplane and two homes were destroyed by impact forces and a postcrash fire. The personal flight was operating under the provisions of 14 Code of Federal Regulations Part 91 on an instrument flight rules flight plan. Visual meteorological conditions prevailed at the time of the accident.
Probable cause
Actions and decisions by National Association for Stock Car Auto Racing's corporate aviation division's management and maintenance personnel to allow the accident airplane to be released for flight with a known and unresolved discrepancy, and the accident pilots' decision to operate the airplane with that known discrepancy, a discrepancy that likely resulted in an in-flight fire.
The Safety Board's full report is available at http://www.ntsb.gov/publictn/A_Acc1.htm. The Aircraft Accident Report number is NTSB/AAR-09-01.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC07MA162
- Event ID
- 20070723X00973
- Case number
- NYC07MA162
- 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: ceddafe843a327c8d69d4b69782369a5ca7f73ebe9b37527dc69e94973144981; retrieved 2026-09-20T16:29:46.023Z.