19981229044079A

Accident · Substantial damage

FAA accident report · Amtr VELITY173ERG · San Diego, CA · December 29, 1998

Date
December 29, 1998 · 15:47 local
Place
San Diego, CA
Airport
Montgomery Field Airport
Phase of flight
Roll-Out (Fixed Wing)
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N466MF
NTSB investigation
NTSBLAX99LA060
Reported as
Amtr VELITY173ERG
Reported engine
Franklin 6A350*
People aboard
3
Fatal injuries
0
Pilot’s flight hours
398 total75 in this make and model42 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(.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.'

As the FAA filed it

(.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.'

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other reports on N466MF · 1

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