The U.S. aircraft register, updated daily
Accidents · NTSB OPS12IA041 · Final report

Cessna 172S and Cessna 172S incident near Daytona Beach, Florida, October 15, 2011

On October 15, 2011 at about 2:08 am local time, 2 aircraft, Cessna 172S (N488ER) and Cessna 172S (N551ER), were involved in the same incident near Daytona Beach, Florida (Daytona Beach International airport). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The departing pilot's incorrect runway selection and non-compliance with an air traffic control clearance. Contributing to the incident was the air traffic controller's inadequate monitoring of the departing aircraft to ensure that the pilot complied with the clearance issued and his failure to issue conflict resolution advisories.
The departing pilot's incorrect runway selection and non-compliance with an air traffic control clearance. Contributing to the incident was the air traffic controller's inadequate monitoring of the departing aircraft to ensure that the pilot complied with the clearance issued and his failure to issue conflict resolution advisories.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 15, 2011 · about 2:08 am local time
Place
Daytona Beach, Florida · Daytona Beach International · map
Type
Incident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft 1
Cessna 172S · all 172Ss on the register
Registration
N488ER · registry record · serial 172S10555
Damage
Not recorded
Flight
Instructional flight · general aviation rules (Part 91)
Aircraft 2
Cessna 172S · all 172Ss on the register
Registration
N551ER · registry record · serial 172S10548
Damage
Not recorded
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative for the Cessna 172S final · quoted from the NTSB record

A local controller cleared the Cessna 172 for takeoff on runway 7L; however, the pilot instead departed from runway 25R and passed within about 400 feet vertically and 500 feet laterally of another Cessna 172 that was turning on final approach to runway 7L. The air traffic controller responsible for the two aircraft did not notice that the pilot of the departing aircraft was using the wrong runway and did not intervene to resolve the conflict with the arriving aircraft. The local controller failed to maintain situational awareness of the airplanes in his Class C airspace and failed to provide timely actions, instructions, or advisories that would have assisted the pilots in identifying the conflict in order to resolve it.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The NTSB's narrative for the Cessna 172S final · quoted from the NTSB record

A local controller cleared the Cessna 172 for takeoff on runway 7L; however, the pilot instead departed from runway 25R and passed within about 400 feet vertically and 500 feet laterally of another Cessna 172 that was turning on final approach to runway 7L. The air traffic controller responsible for the two aircraft did not notice that the pilot of the departing aircraft was using the wrong runway and did not intervene to resolve the conflict with the arriving aircraft. The local controller failed to maintain situational awareness of the airplanes in his Class C airspace and failed to provide timely actions, instructions, or advisories that would have assisted the pilots in identifying the conflict in order to resolve it.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record for the Cessna 172S from the NTSB's investigation tables, in plain English

What happened, in order

  1. Miscellaneous/other during takeoff defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Incorrect action sequence › Pilot
  • factor Personnel issues › Action/decision › Info processing/decision › Identification/recognition › ATC personnel

The aircraft

  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-L2A (piston); 0 hours total
  • Operator: Embry Riddle Aeronautical University

The flight

  • Departed from: DAB Daytona Beach FL
  • Destination: DAB Daytona Beach FL
  • Flight plan: not recorded

Weather at the time

  • Light: night
  • Visibility: 10 statute miles
  • Sky: a few clouds at 7,000 ft
  • Temperature: 66°F (19°C), dew point 63°F (17°C)
  • Altimeter: 29.92 inHg
  • Observation at 1:53 am from KDAB

Injuries

FatalSeriousMinorNone
Flight crew1

The factual record for the Cessna 172S from the NTSB's investigation tables, in plain English

What happened, in order

  1. Near midair/TCAS alert/loss of separation during approach (VFR pattern final) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Incorrect action sequence › Pilot of other aircraft
  • factor Personnel issues › Action/decision › Info processing/decision › Identification/recognition › ATC personnel

Crew member

No details recorded.

The aircraft

  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-L2A (piston); 0 hours total

The flight

  • Departed from: DAB Daytona Beach FL
  • Destination: DAB Daytona Beach FL
  • Flight plan: not recorded
  • A second pilot was aboard

Injuries

FatalSeriousMinorNone
Flight crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.