# Incident 20200126008799I: Piper PA-28R-201, Oakland, CA, January 26, 2020

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 26, 2020, 18:13 local time
- Place: Oakland, CA
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 37.8044° N, 122.2708° W: Placed by OpenAirDocs: center of Oakland, CA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.8044&lon=-122.2708&mi=10
- Aircraft: N2103M, registered now (https://openairdocs.org/aircraft/N2103M) (OpenAirDocs)
- Registry model: Piper PA-28R-201 (registry code 7102816, https://openairdocs.org/model/piper-pa-28r-201) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: PIPER PA-28R-201
- Reported engine: LYCOMING I0360 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport, commercial pilot, flight instructor
- Pilot flight hours: 2,829 total, 497 in this make and model, 33 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20200126008799I

## Narrative

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

PILOT'S STATEMENT:

COMING BACK FROM A VFR FLIGHT FROM SANTA ROSA TO OAKLAND (KOAK). I ASKED FOR PATTERN WORK AND WAS "CLEARED FOR THE OPTION ON 28 L" WITH A LEFT PATTERN (NOTE: THE LEFT PATTERN IS AT 600 AGL AND VERY TIGHT BECAUSE PILOTS ARE REQUIRED TO STAY NORTH OF THE TOWER). ON THE DEPARTURE LEG AFTER THE THIRD ROUND (2 TOUCH AND GO'S, 1 LOW APPROACH, I ASKED THE CONTROLLER (WHILE I WAS ON DEPARTURE LEG FROM 28L) ?N2103M, ON THE NEXT ONE, REQUEST RUNWAY 33, FULL STOP". THE CONTROLLER SAID "YOU CAN EXPECT THIS ON YOUR NEXT TOUCH-AND-GO"). I CONTINUED TO FLY THE LEFT PATTERN.  ON DOWNWIND, THE CONTROLLER ASKED ME "CAN YOU ACCEPT A SHORT APPROACH?? I VERIFIED: "TO RUNWAY 33?? SHE CONFIRMED AND CLEARED ME TO LAND ON 33. I WAS ON LEFT DOWNWIND FOR 28L, APPROXIMATELY AT THE EXTENDED CENTERLINE FOR 33 AT 600 FT. AND TURNED LEFT.  I WAS RELATIVELY HIGH FOR RWY 33 (ABOUT A HALF A MILE OR LESS FROM THE THRESHOLD)  AND MADE A PRE-PLANNED DECISION TO PERFORM A GO-AROUND, IF I WAS UNABLE TO TOUCH DOWN AT A NORMAL SPEED IN THE FIRST 30 % OF THE RUNWAY. I CONCENTRATED ON MY APPROACH ANGLE AND SPEED AND REALIZED I WOULD TOUCH DOWN BEFORE MY PRE-DEFINED LIMIT.

TOUCHDOWN WAS NORMAL ON THE MAIN GEAR AFTER ABOUT A QUARTER OF THE RUNWAY, BUT WHEN I GENTLY LOWERED THE NOSE, THE PROP STRIKE RESULTED. THEN I IMMEDIATELY HELD THE YOKE BACK AND HAD NO IDEA WHY THE PROP STRIKE HAPPENED BUT COULD NOW FEEL THE NOSE GEAR EXTENDING FURTHER. THE NOSE GEAR NEVER DID COLLAPSE. I TAXIED OFF THE RUNWAY WITH A RIGHT TURN ON TAXIWAY D. I SHUT OFF THE ENGINE AND REQUESTED A TUG.

I REALIZED LATER THAT WHILE I WAS CONCENTRATING ON THE UNUSUAL SHORT APPROACH, I HAD FORGOTTEN TO MOVE THE GEAR LEVER TO THE DOWN POSITION.  THE AUTOMATIC GEAR-EXTENSION SYSTEM OF MY AIRPLANE DEPLOYED AND PUT THE MAIN GEARS DOWN, BUT THE NOSE WHEEL WAS NOT FULLY EXTENDED ON TOUCH DOWN, CAUSING THE PROP STRIKE.

WEATHER CONDITIONS WERE VFR WITH LIGHT WIND FROM ABOUT 270. TIME WAS ABOUT 17:20. I WAS THE ONLY OCCUPANT OF THE AIRPLANE.

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.