# Incident 20180218002749I: Cessna 152, Valkaria, FL, February 18, 2018

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 18, 2018, 10:00 local time
- Place: Valkaria, FL
- Airport: Valkaria
- Damage: Minor damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 27.9609° N, 80.5583° W: Placed by OpenAirDocs at VALKARIA (X59), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=27.9609&lon=-80.5583&mi=10
- Aircraft: N94768, registered now (https://openairdocs.org/aircraft/N94768) (OpenAirDocs)
- Registry model: Cessna 152 (registry code 2071835, https://openairdocs.org/model/cessna-152) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: CESSNA 152
- Reported engine: LYCOMING 0-235 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20180218002749I

## Narrative

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

IN THE MORNING OF FEBRUARY 18, 2018, A STUDENT PILOT AND HIS FLIGHT INSTRUCTOR DEPARTED VALKARIA AIRPORT TO THE PRACTICE AREA IN A CESSNA 152. BETWEEN 0900 AND 1000. THEY RETURNED TO THE AIRPORT IN ORDER FOR THE STUDENT TO PRACTICE A FEW MORE TOUCH AND GO LANDINGS. AT 1000 FEET WHILE FLYING IN THE TRAFFIC PATTERN, SUDDENLY, THEY HEARD A STRANGE NOISE, AND THE STUDENT FELT THAT THE AIRCRAFT NEEDED MORE TRIMMING THAN BEFORE. THE FLIGHT INSTRUCTOR TOOK OVER THE FLIGHT CONTROLS BUT COULD NOT DETECT ANYTHING UNUSUAL. DURING THE POST FLIGHT INSPECTION THEY FOUND A BULLET HOLE ON THE LEFT SIDE OF THE RUDDER AND A PROTUSION ON THE RIGHT SIDE OF THE RUDDER. IT APPEARED THAT THE BULLET WAS STILL INSIDE THE RUDDER.

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.