# Incident 20020406013349I: Cessna 172S, Cambridge, MD, April 6, 2002

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 6, 2002, 10:45 local time
- Place: Cambridge, MD
- Airport: Cambridge Dorchester Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 38.5393° N, 76.0304° W: Placed by OpenAirDocs at CAMBRIDGE-DORCHESTER RGNL (CGE), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.5393&lon=-76.0304&mi=10
- Aircraft: N3501J, a cancelled registration (https://openairdocs.org/deregistered/N3501J-2006-05-10) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- People aboard: 2
- Fatal injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 36 total, 36 in this make and model, 20 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020406013349I

## Narrative

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

(-23) PILOT AND PASSENGER LEFT MTN FOR A FLIGHT TO CGE. FLIGHT WAS NORMAL AND HE ENTERED PATTERN AT CGE. PILOT SAID WIND WAS RIGHT DOWN THE RUNWAY AS HE FLEW OVER THE AIRPORT. FINAL APPROACH WAS BUMPY AND WHEN HE CROSSED THE NUMBERS HE HAD AN UNEXPECTED CROSSWIND AND WAS ALMOST BLOWN OFF THE RUNWAY. POWER WAS ADDED TO REALIGN WITH THE RUNWAY AND THEN REDUCED AND HE FLARED THE AIRCRAFT TOO HIGH AND IT DROPPED ONTO THE RUNWAY. POWER WAS ADDED TO STOP ANY FURTHER BOUNCING. THE AIRCRAFT WAS TAXIED TO THE RAMP. DURING MY CONVERSATION WITH THE PILOT, HE TOLD ME HE HAD 36 HOURS TOTAL TIME. I DISCUSSED THE SUBJECT OF HIM NOT BEING ABLE TO CARRY PASSENGERS AND HE SAID HE WAS NOT AWARE OF THAT. I STATED THAT HE MAY BE IN VIOLATION FOR CARRYING A PASSENGER. I ASKED HIM TO PUT TOGETHER A STATEMENT OF WHAT TRANSPIRED THAT DAY AND SEND IT TO THIS OFFICE. THE PILOT DID PUT A STATEMENT TOGETHER AND SENT IT TO THIS OFFICE. THIS INFORMATION HAS BEEN FORWARDED TO OFFICE MANAGEMENT FOR POTENTIAL ENFORCEMENT ACTION.

## Other reports on N3501J (1)

Matched to the same aircraft by N-number and date.

- [Incident 20051111032449I](https://openairdocs.org/incident/20051111032449I), Nov 11, 2005: Cessna 172S (N3501J), Church Hill, MD. (-23) Flight instructor was simulating a forced landing. After the student had completed the procedures of the forced landing, the aircraft was at an altitude…

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.