FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC08FA054 · Piper PA-30

8 Dec 2007 · Parkland, FL, United States

Piper PA-30 and Rohan Aviation Cessna 152 · Accident: midair collision en route

Report a problem

Event

NTSB case
NYC08FA054
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
2 · 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 · Piper PA-30

Aircraft type
Piper PA-30
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
N766CC
Onboard fatalities
Unknown
Route
From Ocala International Airport - Jim Taylor Field (OCF), Ocala, FLTo Pompano Beach Airpark (PMP), Pompano Beach, 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
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 152

Aircraft type
Cessna 152
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
N24478
Onboard fatalities
Unknown
Route
From Palm Beach County Park Airport (LNA), Lantana, FLTo Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, 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
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

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

A low-wing, twin-engine Piper PA-30, piloted by a certificated private pilot, was operating on an instrument-flight-rules flight plan. A high-wing, single-engine Cessna 152, piloted by a certificated student pilot, was operating on a visual-flight-rules solo instructional flight. The Cessna student pilot was not communicating with air traffic control, nor was he required to. Both airplanes were operating in visual meteorological conditions. Both airplanes were also level at 2,000 feet, although, for undetermined reasons, the altitude encoder of the Cessna indicated that the airplane was 200 feet higher. The air traffic controller controlling the Piper advised the pilot of the presence of traffic, that was ultimately determined to be the Cessna, and the pilot responded that he was looking for it. The controller then turned his attention to other air traffic, and about 1 minute later again advised the Piper pilot of the traffic at 2,200 feet. Immediately after the transmission, a mid-air collision occurred between the two airplanes. Radar data revealed that between the two callouts by the controller, the Cessna had altered its course from a general heading of 220 degrees magnetic to a heading of 177 degrees magnetic. Sun position, about the time of the accident, was 27 degrees above the horizon, bearing about 227 degrees; however, the extent to which the sun factored in the Cessna student pilot's ability to see the Piper is unknown. The Piper pilot was required to wear corrective lenses, however it could not be determined if he was wearing corrective lenses at the time of the accident.

Probable cause

Both pilots' failure to see and avoid the other airplane. Contributing to the accident were the erroneous readouts from the Cessna's altitude encoder.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC08FA054
Event ID
20071227X02001
Case number
NYC08FA054
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: 297c33de6f3ca2f60e69597782a3d6f32a64436a32c64d936a9b1e8e23dfaee1; retrieved 2026-09-20T16:04:06.095Z.