# Incident 20140602008089I: Diamond Aircraft Ind Inc DA 20-C1, Rdu, NC, June 2, 2014

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 2, 2014, 14:37 local time
- Place: Rdu, NC
- Airport: Raleigh-Durham International
- Damage: Minor damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 35.8776° N, 78.7875° W: Placed by OpenAirDocs at RALEIGH-DURHAM INTL (RDU), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.8776&lon=-78.7875&mi=10
- Aircraft: N391JA, a cancelled registration (https://openairdocs.org/deregistered/N391JA-2019-04-29) (OpenAirDocs)
- Registry model: Diamond Aircraft Ind DA20-C1 (registry code 2990001, https://openairdocs.org/model/diamond-aircraft-ind-da20-c1) (OpenAirDocs)
- Registry engine: Continental IO-240 series (registry code 17063, https://openairdocs.org/engine/continental-io-240-series) (OpenAirDocs)
- Reported make and model: DIAMOND AIRCRAFT IND INC DA 20-C1
- Reported engine: CONT MOTOR IO-240 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 79 total, 79 in this make and model, 23 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20140602008089I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

CONTROLLER GAVE PILOT VECTORS THAT SET PILOT  UP ON A RIGHT DOWNWIND FOR RUNWAY 32.  CONTROLLER GAVE HER A CLEARANCE TO DESCEND AT HER DISCRETION.  CONTROLLER CALLED HER BASE LEG.  PILOT INDICATED IN A STATEMENT THAT SHE WAS HIGHER ON BASE THAN SHE WOULD HAVE LIKED.  PILOT PUT THE AIRCRAFT INTO A FORWARD SLIP ON FINAL APPROACH IN ORDER TO LOSE ALTITUDE AS RAPIDLY AS SHE COULD.  PILOT REPORTED BEING TOO FAST AND TOO HIGH.  SHE INITIATED A GO-AROUND.  SHE SET UP ON A DOWNWIND FOR 32, AND REPORTED BEING TOO FAST.  SHE SAID SHE WAS PLANNING TO EXTEND HER DOWNWIND DUE TO BEING TOO FAST.  TOWER INFORMED HER THAT THERE WAS TRAFFIC  INBOUND TO 32 AND SHE NEEDED TO TURN ONTO THE BASE LEG FOR 32 IMMEDIATELY.  SHE SAID SHE WAS STILL TOO FAST FOR LANDING FLAPS.  SHE HAD THE THROTTLE AT IDLE.  ONCE SHE WAS SLOW ENOUGH FOR LANDING FLAPS SHE WAS CONCERNED SHE WOULD RUN OUT OF RUNWAY, SO SHE PUT THE AIRCRAFT IN A NOSE LOW ATTITUDE.  STILL TOO FAST,  THE PILOT ATTEMPTED TO TO LAND BECAUSE ATC HAD ANOTHER AIR PLANE SET UP ON FINAL FOR RUNWAY 32 BEHIND HER.  THE PROPELLER HIT THE RUNWAY.  THE PILOT REPORTED THAT SHE WAS NOT AWARE OF EXACTLY WHAT HAD HAPPENED TO THE PROPELLER.  THE AIRCRAFT HAD BOUNCED BACK INTO THE AIR AND THE PILOT INITIATED A GO-AROUND.  SHE REQUESTED TO LAND ON THE LONGER OF THE RUNWAYS, 23L, AND MADE HER WAY AROUND TO LAND.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.