# Accident 19981229044079A: Amtr VELITY173ERG, San Diego, CA, December 29, 1998

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: December 29, 1998, 15:47 local time
- Place: San Diego, CA
- Airport: Montgomery Field Airport
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 32.8000° N, 117.1295° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=32.8000&lon=-117.1295&mi=10
- Aircraft: N466MF, a cancelled registration (https://openairdocs.org/deregistered/N466MF-2005-05-25) (OpenAirDocs)
- Registry model: Aegerter Simon VELOCITY 173E RG (registry code 05604I3, https://openairdocs.org/model/aegerter-simon-velocity-173e-rg) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: AMTR VELITY173ERG
- Reported engine: FRNKLN 6A350*
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 398 total, 75 in this make and model, 42 in the last 90 days
- NTSB investigation: [NTSB LAX99LA060](https://openairdocs.org/ntsb/LAX99LA060) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19981229044079A

## Narrative

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

(.19) ON DECEMBER 29, 1998, AT 1547 HOURS PACIFIC STANDARD TIME, A VELOCITY 173E-RG, N466MF, VEERED OFF RUNWAY 28L ON LANDING AT MONTGOMERY FIELD, SAN DIEGO, CALIFORNIA, AND COLLIDED WITH A PARKED CESSNA 340, N 6241X. THE AIRCRAFT AND THE PARKED AND UNOCCUPIED CESSNA 340 SUSTAINED SUBSTANTIAL DAMAGE. THE PRIVATE PILOT AND THE TWO PASSENGERS WERE NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED FOR THE PERSONAL FLIGHT FROM TUCSON, ARIZONA, TO MONTGOMERY FIELD. THIS WAS THE LAST LEG OF A CROSS COUNTRY WHICH ORIGINATED THE DAY BEFORE IN TAMPA, FLORIDA. NO FLIGHT PLAN WAS FILED. (.4) THE PILOT STATED HE HAD EXPERIENCED INSUFFICIENT PITCH CONTROL ON LANDING AT TUCSON, ARIZONA, PRIOR TO THE ACCIDENT. HE REPORTED THAT HE 'FOUND PLAY IN THE ELEVATOR CONTROL,' AND WAS ADVISED OVER THE TELEPHONE BY VELOCITY INC. TO ADD WASHERS OR SPACERS TO THE REAR OF THE TORQUE TUBE TO REMOVE THE PLAY. WITH THE AID OF A LOCAL PILOT IN TUCSON, HE ADDED THE WASHERS AND SPACERS TO THE REAR OF THE TORQUE TUBE.  THE PILOT FURTHER STATED THAT UPON ATTEMPTING TO FLARE AT MONTGOMERY FIELD, 'THE NOSE WOULD NOT COME UP.'  THE AIRCRAFT BOUNCED, VEERED OFF THE RUNWAY, SKIDDED ACROSS A GRASS AREA, AND COLLIDED  TAIL FIRST WITH A PARKED CESSNA 340. ACCORDING TO THE PILOT, ON JANUARY 2, 1999, BUILDERS FROM VELOCITY INC. INSPECTED THE AIRPLANE, AND FOUND THAT 'THE FRONT BEARING OF THE AILERON TORQUE TUBE HAD COME LOOSE, THUS PREVENTING A FULL ELEVATOR DOWN DEFLECTION.'

## 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 LAX99LA060](https://openairdocs.org/ntsb/LAX99LA060), Dec 29, 1998: Aegerter, Simon Velocity 173E-RG (N466MF), San Diego, CA, substantial damage. Probable cause: The pilot's inadequate modification to the control systems, which resulted in a restricted elevator control.

## Other reports on N466MF (1)

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

- [Incident 20010328006729I](https://openairdocs.org/incident/20010328006729I), Mar 28, 2001: Amtr VELITY173ERG (N466MF), Leslie, GA, Minor damage. (-23) At 0430PM on 3/28/01 velocity 173E N466MF experienced a loss of engine power 3000 ft above Leslie, GA. The pilot elected to land gear up in a wheat…

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.