# Incident 20240101000519I: Martino Thomas G VELCITY 173 ELITE RG, Santa Rosa, CA, January 1, 2024 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: January 1, 2024, 12:00 local time - Place: Santa Rosa, CA - Damage: Minor damage - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Location: 38.4405° N, 122.7144° W: Placed by OpenAirDocs: center of Santa Rosa, CA, within about 6 miles (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=38.4405&lon=-122.7144&mi=10 - Aircraft: N173EX, registered now (https://openairdocs.org/aircraft/N173EX) (OpenAirDocs) - Registry model: Martino Thomas G VELCITY 173 ELITE RG (registry code 05618OX, https://openairdocs.org/model/martino-thomas-g-velcity-173-elite-rg) (OpenAirDocs) - Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs) - Reported make and model: MARTINO THOMAS G VELCITY 173 ELITE RG - Reported engine: LYCOMING IO-540 SER - People aboard: 2 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Private pilot - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20240101000519I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (STATEMENT FROM PILOT) UPON ENTERING THE PATTERN, I TRIED TO LOWER THE LANDING GEAR AND UPON CHECKING THE GEAR INDICATOR LIGHT I OBSERVED THAT THE NOSE GEAR WAS INDICATING THAT IT WAS NOT DOWN. I HEADED BACK TO SANTA ROSA. UPON CONTACTING THE TOWER, I INFORMED THEM THAT I WANTED TO DO A FLY BY AND HAVE THEM CONFIRM THE GEAR. AFTER THE LOW PASS AND THE TOWER CONFIRMING THAT THE NOSE GEAR WAS STILL UP, I CLIMBED ABOVE THE AIRPORT AND DID SOME TROUBLESHOOTING (CYCLED GEAR, TRIED DUMP VALVE, DID HIGH G PULL UPS) ALL WITH NO SUCCESS. THE TOWER WENT AHEAD AND DECLARED AN EMERGENCY FOR ME AND HAD THE FIRE TRUCKS WAITING ON RUNWAY 02. I NEXT TRIED A RELATIVELY HARD TOUCH AND GO HOPING TO DISLODGE THE NOSE GEAR BUT WITHOUT SUCCESS. I THEN WENT AROUND THE PATTERN AND PERFORMED A NOSE GEAR UP LANDING. AFTER TOUCHDOWN I KEPT THE NOSE UP AS LONG AS I COULD BEFORE THE NOSE DROPPED TO THE RUNWAY AND WE SKIDDED TO A STOP. BACKGROUND: PRIOR TO THE INCIDENT, ON DECEMBER 23, 2023, I COMPLETED THE INSTALLATION OF A NEW MACHINED NOSE WHEEL FORK WITH SHIMMY DAMPER. VELOCITY AIRPLANES HAVE HAD MANY DOCUMENTED CASES OF NOSE WHEEL SHIMMY EVENTS THAT RESULT IN THE LANDING GEAR LEG OR CAST ALUMINUM FORK FAILING. THE ORIGINAL NOSE FORK REQUIRED TIGHTENING THE BELLVILLE WASHERS SO THAT IT TOOK APPROXIMATELY 15 LBF TO ROTATE THE FORK AND PREVENT SHIMMY. THE NEW FORK ASSEMBLY WITH DAMPER REQUIRES MINIMAL FORCE TO TURN THE PLANE WHEN TAXIING. AFTER INSTALLATION OF THE NEW FORK ASSEMBLY, THE GEAR WAS CYCLED WITHOUT INCIDENT AND A TEST FLIGHT WAS PERFORMED VERIFYING PROPER FUNCTION. FINDINGS: AFTER HAVING THE AIRPLANE REMOVED FROM THE RUNWAY AND RETURNED TO MY HANGER, I OBSERVED A SMALL MARK ON THE SIDE OF THE NOSE GEAR FORK. I THEN PUT THE PLANE ON JACKS AND CYCLED THE GEAR. I OBSERVED THAT THE NOSE FORK ASSEMBLY CAN ROTATE SLIGHTLY IN BOTH DIRECTIONS WITHIN THE WHEEL WELL. WHEN THE FORK ROTATES TO THE RIGHT AND THE GEAR IS LOWERED, THE EDGE OF THE FORK CAN CATCH ON THE CORNER OF THE TRAY THAT SUPPORTS THE BACKUP BATTERY. (SEE IMAGES BELOW) CONCLUSION: WITH THE INSTALLATION OF THE NEW NOSE GEAR FORK ASSEMBLY, IT IS BELIEVED THAT THE FORK ASSEMBLY ROTATED IN THE WHEEL WELL. THIS ROTATION PROBABLY RESULTED FROM THE FREE CASTERING OF THE NOSE FORK ALONG WITH THE ANGULAR MOMENTUM OF THE SPINNING NOSE WHEEL. ONCE THE FORK HAD ROTATED IT BECAME LOCKED AGAINST THE BATTERY TRAY PREVENTING EXTENSION OF THE LANDING GEAR. TO ELIMINATE THE ISSUE THE BATTERY TRAY WILL BE MODIFIED TO REMOVE THE CORNER THAT THE FORK WAS CATCHING ON. ## Other reports on N173EX (1) Matched to the same aircraft by N-number and date. - [Incident 20070816017339I](https://openairdocs.org/incident/20070816017339I), Aug 16, 2007: Amtr VELITY173ERG (N173EX), Denver, CO, Minor damage. (-23) Aircraft was climbing out after takeoff. Upon reaching approximately 300FT AGL on an easterly heading the aircraft experienced an abrupt power loss. The… 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.