# Accident 20070309003189A: Cessna 172R, Norfolk, VA, March 9, 2007

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 9, 2007, 12:55 local time
- Place: Norfolk, VA
- Airport: Norfolk International
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 36.8947° N, 76.2014° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.8947&lon=-76.2014&mi=10
- Aircraft: N441QF, registered now (https://openairdocs.org/aircraft/N441QF) (OpenAirDocs)
- Registry model: Cessna 172R (registry code 2072401, https://openairdocs.org/model/cessna-172r) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: CESSNA 172R
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 263 total, 190 in this make and model, 41 in the last 90 days
- NTSB investigation: [NTSB NYC07CA078](https://openairdocs.org/ntsb/NYC07CA078) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20070309003189A

## Narrative

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

(-23) UPON LANDING (RWY 5), THE PILOT IN COMMAND (PIC) FELT UNBALANCED AND LOST DIRECTIONAL CONTROL. TRIED TO CORRECT WITH RUDDER AND WENT OFF THE RUNWAY AND HIT THE 7000' REMAINING SIGN. PLANE SWIVELED TO THE RIGHT AND CAME TO REST. PIC HAD TO BE PRYED OUT OF THE AIRCRAFT BY ARFF. WINDS 110 @ 7.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB NYC07CA078](https://openairdocs.org/ntsb/NYC07CA078), Mar 9, 2007: Cessna 172R (N441QF), Norfolk, VA, substantial damage. Probable cause: The pilot's failure to maintain directional control while landing, which resulted in a collision with a runway sign. A factor was the crosswind.

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.