Montgomery Field Airport, San Diego, CA

Location :

History :

Montgomery Field Airport Today:




Airport Services and Amenities:
Special Events:

Airport Area Accident History:
Accident occurred Tuesday, June 24, 2008 in San Diego, CA
Probable Cause Approval Date: 7/30/2008
Aircraft: Cessna 172M, registration: N9629V
Injuries: 1 Uninjured.
The student pilot reported that he was practicing touch-and-go landings and made a normal landing on runway 28L. Witnesses located adjacent to the runway observed the landing, and stated that the airplane landed hard on the right main landing gear. During the landing roll, the pilot raised the flaps, turned the carburetor heat off, and started to increase engine power when the airplane then began to veer to the left. He then applied full engine power in an attempt to get the airplane airborne. The airplane became airborne and the left main landing gear struck a taxiway sign. The pilot then elected to abort the takeoff and he reduced engine power, switched off the master switch and turned off the magnetos. The airplane continued into the adjacent ramp area and struck a parked and unoccupied helicopter.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The student pilot's failure to maintain directional control during a touch-and-go landing.

= = =
Accident occurred Thursday, January 11, 2007 in San Diego, CA
Probable Cause Approval Date: 8/30/2007
Aircraft: Cessna TR182, registration: N5443S
Injuries: 1 Serious.
The airplane impacted the runway in a nose-down attitude during the takeoff initial climb out. The 79-year old pilot was departing on a short flight to his home airport when the accident occurred. According to a witness, the airplane climbed to 100 feet and suddenly pitched nose-down. The airplane continued in this attitude until ground impact. Post accident examination of the airplane control systems did not reveal any operational anomalies. Investigators noted that the trim tab was set 10 degrees nose down and the flaps were extended to 40 degrees. Both of these control positions are inconsistent with normal takeoff settings as specified by the airplane manufacturer.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot's failure to maintain control of the airplane during takeoff. A contributing factor to the accident was the improper takeoff configuration of the airplane.

= = =
Accident occurred Friday, October 13, 2006 in San Diego, CA
Probable Cause Approval Date: 2/26/2007
Aircraft: Finney Thorp T-18, registration: N467JF
Injuries: 1 Uninjured.
The airplane ground looped during the landing rollout and the right wing was bent. The pilot reported that the approach and touchdown were normal, but he lost directional control during the rollout due to crosswind conditions. The pilot stated that there were no mechanical anomalies with the airplane.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

the pilot's inadequate compensation for the crosswind conditions and failure to maintain directional control during landing.

= = =
Accident occurred Sunday, November 19, 2006 in San Diego, CA
Probable Cause Approval Date: 11/29/2007
Aircraft: Cessna 172RG, registration: N28RJ
Injuries: 4 Uninjured.
According to a report obtained from the airport manager, the airplane experienced a complete electrical failure during the flight. The pilot elected to return and land at the departure airport. After receiving a clearance to land from the tower (via light gun signal), the pilot prepared for landing and moved the landing gear handle to the down position. The landing gear dropped from their bays, but did not extend and lock into place. The pilot did not pump the emergency landing gear extension handle to lock the landing gear in the down position. As the aircraft touched down on the runway, the main landing gear legs folded back into their retracted position. The left wing and horizontal stabilizer contacted the runway as the aircraft came to a stop in an upright position. The airplane sustained substantial damage to its left horizontal stabilizer. The reason for the electrical failure was not determined.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

An undetermined total electrical failure. The pilot's failure to extend the landing gear to the down and locked position was a factor.

= = =
Accident occurred Monday, May 08, 2006 in San Diego, CA
Probable Cause Approval Date: 7/25/2007
Aircraft: McKenzie Lancair IV-P Turbine, registration: N5M
Injuries: 1 Uninjured.
The airplane veered off the runway after the left main gear collapsed on landing. The pilot was cleared to land on runway 28L. He lowered the landing gear in preparation for landing, and received an indication of three green lights confirming that the gear was down and locked. At this point, an electrical power failure occurred, and he initiated a go-around. He turned the emergency battery on, and this restored power to the radio and several critical systems. The gear lights indicated that only the nose and right main were now down and locked. He asked the tower controller to confirm the gear position. The tower said it appeared to be down, and cleared the pilot to land on runway 28R. Upon touchdown, the left main gear collapsed. The pilot stated that he should have tried to pump the gear in an attempt to get it in the locked position. No determination was made regarding the reason for the collapse of the left main landing gear.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The collapse of the left main gear for undetermined reasons. A factor was the pilot's inadequate remedial action in response to the left main gear not locked warning light by not attempting to manually extend the gear to ensure it was fully down and locked.

= = =
Accident occurred Monday, March 27, 2006 in San Diego, CA
Probable Cause Approval Date: 8/29/2006
Aircraft: Claypool RV-6A, registration: N428BC
Injuries: 1 Minor.
The solo private pilot was landing on a hard surfaced runway at the conclusion of a Title 14, CFR Part 91 personal cross-country flight in an experimental, amateur built airplane. He said during landing he overshot the final approach course, and in an attempt to salvage the landing, he forgot to put in the last notch of flaps. He said the airplane crossed the threshold too fast and would not slow down. He stated that the airplane landed hard, and then porpoised. On the third bounce, he said the nose wheel collapsed, and the airplane nosed over. He said he should have gone around and reconfigured the airplane instead of attempting to land. The pilot reported that there were no mechanical anomalies with the airplane prior to the accident. He said the airplane sustained structural damage to the nose gear, wings, and fuselage.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot's improper recovery from a bounced landing, which resulted in a hard landing, the collapse of the nose landing gear, and a nose over. A factor associated with the accident was the pilot's failure to perform a go-around.

= = =
Accident occurred Saturday, November 13, 2004 in San Diego, CA
Probable Cause Approval Date: 12/28/2006
Aircraft: Great Lakes 2T-1A, registration: N502GL
Injuries: 2 Uninjured.
On the landing rollout the airplane ground looped. The certified flight instructor (CFI) reported that he was demonstrating a forward slip to lose altitude for landing. As the airplane was rolling out, he attempted to slow down by adding light pressure on both heel brakes. The airplane began a right turn, and he counteracted with additional pressure on the left brake, but there was no response. The airplane swerved off the runway and ground looped. A Federal Aviation Administration inspector examined the airplane's brake system. When he depressed the brakes he found them a little spongy but completely operational.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

the flight instructor's failure to maintain directional control during the landing rollout.

= = =
Accident occurred Friday, July 23, 2004 in San Diego, CA
Probable Cause Approval Date: 3/28/2006
Aircraft: Cessna 172RG, registration: N5167R
Injuries: 1 Uninjured.
The right main landing gear collapsed during rollout following a normal touchdown on the runway. Thereafter, directional control was lost, and the right wing struck the surface of the runway. The airplane veered off the runway, and it came to rest in an adjacent open dirt field. During flight the pilot had experienced a low voltage condition, and his radio communications became problematic as the battery gradually discharged. The pilot cycled the airplane's master electric system switch in accordance with instructions in the Cessna Pilot's Operator's Handbook. Because this did not restore electric power, the pilot reduced the electrical load to conserve energy. No evidence of any mechanical malfunction was found during the post impact examination of the landing gear and alternator/battery electric system. During the examination the alternator field circuit breaker was found in the tripped position. The examination revealed that when the alternator
circuit breaker was reset, electric current was restored to the buss and the battery was charging. Prior to landing, the pilot failed to properly perform procedures relating to ensuring that the alternator circuit breaker was engaged. Also, the pilot failed to ensure that the landing gear was fully extended by using the emergency gear extension system.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot's failure to ensure that the landing gear was fully extended, by use of the emergency gear extension system, which resulted in its partial collapse during landing rollout. Also causal was the pilot's failure to follow POH procedures relating to troubleshooting and restoring electric power to the airplane busses.

= = =
Accident occurred Sunday, January 11, 2004 in San Diego, CA
Probable Cause Approval Date: 4/28/2004
Aircraft: Cessna 152, registration: N67844
Injuries: 1 Uninjured.
The airplane collided with a fuel truck while taxing to parking. While taxiing on the ramp area, between rows of parked airplanes, the pilot noticed a parked fuel truck ahead of her on the left side. After deciding she had adequate clearance between the airplane and the fuel truck, she continued taxiing and momentarily glanced down at the airplane's checklist. She stated that she "incorrectly judged" the distance between the airplane and fuel truck, and the airplane struck the fuel truck with the outboard section of the left wing. The pilot reported no preimpact mechanical malfunctions or failures with the airplane.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

the pilot's misjudgment of clearance from the vehicle while taxiing. A factor in the accident was the pilot's diverted attention.

= = =
Accident occurred Sunday, October 19, 2003 in San Diego, CA
Probable Cause Approval Date: 2/24/2005
Aircraft: Cessna 170, registration: N3979V
Injuries: 1 Uninjured.
The airplane ground looped off the runway when the pilot's seat slid aft during landing. The pilot said that when he flared for landing he heard a "click" and then his seat slid backwards about 1 foot, restricting his ability to reach the controls. The pilot tried to adjust his seat position to regain access to the airplane's controls, but the airplane entered a left ground loop and came to rest left of the runway. A Federal Aviation Administration inspector examined and photographed the pilot's seat. He reported that the seat track locking pin was positioned outside the seat track. He observed that the side floor deck was buckled, the seat was structurally deformed, and the seat locking pin was outside the seat rail and roller, all indicative of impact related damage. The inspector stated that he could not make a reliable determination of pin position prior to the impact damage.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

the pilot's inadequate preflight inspection which failed to determine the security of his seat, and his failure to maintain directional control.

= = =
Accident occurred Saturday, October 25, 2003 in San Diego, CA
Probable Cause Approval Date: 3/30/2004
Aircraft: Piper PA 28-161, registration: N39494
Injuries: 2 Uninjured.
A Cessna 172R, N72AF, and a Piper PA-28-161, N39494, collided during taxi. The left wing and the propeller of the Piper respectively struck the rudder and right aileron of the Cessna. According to the pilot of the Piper, after arriving at the run-up area, the pilot attempted to slow the airplane. Instead of using the brake pedals, he used the rudder pedals. The pilot closed the throttle, but was unable to prevent the collision. The pilot did not report any mechanical malfunctions with the airplane.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

the student pilot's inadvertent application of the rudder pedals rather than the brakes, which resulted in the on ground collision with the Cessna 172R.

= = =
Accident occurred Tuesday, December 09, 2003 in San Diego, CA
Probable Cause Approval Date: 3/30/2004
Aircraft: Beech 58P, registration: N58JG
Injuries: 2 Uninjured.
The airplane collided with a parked, unoccupied, vehicle while taxiing to the active runway. The pilot said that while taxiing, he noticed a red truck parked on the right side of the taxiway. He maneuvered the airplane so that the nose gear was about 1 foot to the left of the taxiway centerline, and attempted to avoid the vehicle. He estimated that he was taxiing about 7 miles per hour when the right wing contacted the truck's cab and he felt the airplane suddenly veer sharply to the right. The right propeller made contact with the front of the truck, and he applied the brakes. After the airplane came to a complete stop, he shut down both engines. The pilot stated that there were no preimpact mechanical malfunctions or failures with the airplane.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

the pilot's inadequate lookout, which resulted in his failure to maintain clearance from the vehicle while taxiing.

= = =
Accident occurred Tuesday, December 09, 2003 in San Diego, CA
Probable Cause Approval Date: 3/30/2004
Aircraft: Beech 58P, registration: N58JG
Injuries: 2 Uninjured.
The airplane collided with a parked, unoccupied, vehicle while taxiing to the active runway. The pilot said that while taxiing, he noticed a red truck parked on the right side of the taxiway. He maneuvered the airplane so that the nose gear was about 1 foot to the left of the taxiway centerline, and attempted to avoid the vehicle. He estimated that he was taxiing about 7 miles per hour when the right wing contacted the truck's cab and he felt the airplane suddenly veer sharply to the right. The right propeller made contact with the front of the truck, and he applied the brakes. After the airplane came to a complete stop, he shut down both engines. The pilot stated that there were no preimpact mechanical malfunctions or failures with the airplane.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

the pilot's inadequate lookout, which resulted in his failure to maintain clearance from the vehicle while taxiing.

= = =
Accident occurred Sunday, December 14, 2003 in Claremont, CA
Probable Cause Approval Date: 5/29/2007
Aircraft: Cessna 421C, registration: N6887L
Injuries: 1 Fatal.
The airplane impacted a residence during a missed approach. After completing the en route portion of the instrument flight, a controller cleared the pilot to proceed direct to the initial approach fix for the global positioning satellite (GPS) approach to the airport. After being cleared for the approach, the airplane continued on a course to the east and at altitudes consistent with flying the GPS published approach procedure. Radar data indicated that at the missed approach point at the minimum descent altitude of 2,000 feet msl, the airplane made a turn to the left, changing course in a northerly direction toward rapidly rising mountainous terrain. The published missed approach specified a climbing right turn to 4,000 feet, and noted that circling north of the airport was not allowed. Remaining in a slight left turn, the airplane climbed to 3,300 feet msl over the duration of 1 minute 9 seconds. The controller advised the pilot that he was flying off
course toward mountainous terrain and instructed him to make an immediate left turn heading in a southbound direction. The airplane descended to 3,200 feet msl and made a left turn in a southerly direction. The airplane continued to descend to 2,100 feet msl and the pilot read back the instructions that the controller gave him. The airplane then climbed to 3,300 feet, with an indicated ground speed of 35 knots, and began a sharp left turn. It then descended to impact with a house. At no time during the approach did the pilot indicate that he was experiencing difficulty navigating or request assistance. An examination of the airplane revealed no evidence a mechanical malfunction or failures prior to impact; however, both the cockpit and instrument panel sustained severe thermal damage, precluding any detailed examinations.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

the pilot became lost/disoriented during the approach, failed to maintain course alignment with the missed approach procedure, and subsequently lost control of the airplane.

= = =
Accident occurred Thursday, May 16, 2002 in SAN DIEGO, CA
Probable Cause Approval Date: 11/25/2003
Aircraft: Cessna 182Q, registration: N9031U
Injuries: 1 Uninjured.
The plane overran the runway after making a full-stop landing. The pilot was intending to do touch-and-go landings, but decided to make his landing a full-stop due to the glare from the sun. After he touched down, the glare from the sun was so intense he had to move up in the seat, slipping his feet off the rudder pedals. He couldn't stop the airplane and ran off the end of the runway into a light pole.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot's failure to apply continuous brake pressure. Sun glare is a contributing factor.

= = =
Accident occurred Sunday, March 03, 2002 in San Diego, CA
Probable Cause Approval Date: 6/30/2004
Aircraft: Piper PA-28-140, registration: N1775T
Injuries: 1 Uninjured.
The airplane experienced a loss of engine power and impacted terrain about 450 yards from the approach end of the runway. The pilot spent about 1.5 hours reviewing the flight manual for the airplane due to his unfamiliarity with this model. He departed with the left fuel tank selected. He spent about 2 hours flying, and then returned to the departure airport. On his initial descent he switched the fuel selector valve to the right tank. About 1 nm from touchdown, the engine began to lose power. He rechecked that the mixture was rich, and the carburetor heat was on. He contacted the air traffic control tower and declared an emergency. He executed a forced landing short of the runway due to insufficient altitude. The pilot inspected the fuel tanks and observed no fuel in the tanks; however, the airplane was in a nose down, left wing low attitude. An FAA inspector examined the fuel system. He observed fuel in the left tank, but none in the right tank. A post
accident engine ground run-up was conducted utilizing the left tank with no discrepancies noted.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

fuel starvation due to the pilot's mismanagement of the fuel system.

= = =
Accident occurred Saturday, February 09, 2002 in SAN DIEGO, CA
Probable Cause Approval Date: 10/24/2002
Aircraft: Great Lakes 2T-1A-1, registration: N502GL
Injuries: 2 Uninjured.
The airplane veered off the runway, a wheel dug into the dirt, and the airplane nosed over. The accident occurred on the pilot's third landing. He made a good 3-point landing just past the numbers. During the landing roll as the airplane slowed to 5 to 10 mph, a gust of wind hit the tail and the airplane swerved off the runway.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot failed to maintain directional control after encountering a gust of wind during the landing roll. Factors were the unexpected wind gusts and the soft terrain adjacent to the runway.

= = =
Accident occurred Wednesday, January 30, 2002 in San Diego, CA
Probable Cause Approval Date: 10/23/2002
Aircraft: Hillyer XL-RG Velocity, registration: C-FPDL
Injuries: 2 Fatal.
The pilot of the amateur built, experimental airplane, contacted the military tower and said: "... tower this is Canadian papa delta lima with an emergency we've uh run out of fuel." The tower controller gave the pilot the altimeter setting and surface wind and clearance to land on the runway nearest the pilot's position. There was a subsequent conversation between the tower and the pilot a few seconds later regarding the arresting gear in place on the runway during which the pilot said: "we're just hoping we make the runway." The tower controller approved landing on the taxiway. The airplane subsequently impacted an embankment about 200 feet short of the runway threshold in an open, grassy area. An FAA inspector responded to the scene and reported finding only a small amount of fuel (less than 1 quart) in the aircraft. The fuel tanks were not breached. The builder of the airplane said it was equipped with a fuel totalizer system that used capacitance
type fuel quantity sensors and had been carefully calibrated and was quite accurate. Prior to the accident flight, the builder said that he observed the pilot use a plain, uncalibrated stick of wood to measure the fuel quantity during his preflight inspection of the aircraft. No fuel was added. He thought it odd that the pilot used the same, moistened, end of the same stick to measure the quantity in the second tank. The pilot commented they wouldn't be out very long, maybe 1 hour.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot's improper in-flight planning and decision making, which resulted in exhaustion of the airplane's fuel supply and loss of engine power.

= = =
Accident occurred Wednesday, December 19, 2001 in San Diego, CA
Probable Cause Approval Date: 6/25/2003
Aircraft: Cessna T210N, registration: N7AL
Injuries: 3 Uninjured.
The airplane landed long and continued off the end of the runway into a chain link fence. Nighttime darkness prevailed and the airport weather, observed 3 minutes after the accident, was visibility 1/4 statute mile, vertical visibility 100 feet, with temperature and dew point both 9 degrees Celsius. A sheriff's deputy reported from the accident site that the visibility was 50 to 100 yards in fog. The pilot reported that the accident occurred as he was returning to the departure airport following a 40-minute post maintenance checkflight. He received the airport weather from the Automatic Terminal Information Service (ATIS) recording and was aware that ground fog had developed at the airport. He received air traffic clearance and executed the instrument landing system (ILS) approach. At decision height he was still in visual meteorological conditions and the runway and approach lighting were in sight. The pilot continued his descent below decision height
by visual reference and encountered dense fog and severe restriction to visibility at 50 to 75 feet above ground level. The pilot did not feel a go-around was possible at that point and continued the landing approach, landing long on the runway and continuing off the end.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot's failure to land on the runway with sufficient runway remaining as a result of his improper IFR procedure by his failure to maintain visual contact with the runway environment, and to execute a missed approach.

= = =
Accident occurred Thursday, February 15, 2001 in San Diego, CA
Probable Cause Approval Date: 1/23/2002
Aircraft: Cessna 172N, registration: N4922D
Injuries: 2 Uninjured.
During landing rollout, the airplane veered off the runway and collided with obstacles. At the completion of a 3.7-hour-long flight, the tower controller advised the pilot that the local wind was from 270 degrees at 6 knots, and asked him to switch runways to the parallel. After touchdown, the airplane was still traveling about 50 knots when, approaching runway 28L's midfield location, the pilot lost directional control. The left wing rose upward. The airplane veered off the runway and impacted a sign. Airport personnel reported that the collision occurred about 1,000 feet upwind of the runway's threshold. The airplane came to a stop about 550 feet farther upwind of the sign and about 200 feet north of the runway. No mechanical malfunctions were reported with the airplane.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot's failure to maintain directional control of the airplane during landing rollout.

= = =
Accident occurred Thursday, February 08, 2001 in San Diego, CA
Probable Cause Approval Date: 1/23/2002
Aircraft: Piper PA-28-181, registration: N8122G
Injuries: 1 Uninjured.
The pilot repositioned the engine fuel tank selector to what he believed was the opposite wing tank when in the downwind leg of the airport traffic pattern. On the base leg, all engine power was lost and the pilot performed an emergency landing, coming to rest about 1,800 feet short of the runway's threshold. An examination of the airplane revealed fuel in both wing tanks. The pilot acknowledged that he had mispositioned the fuel selector by inadvertently switching it to the off position.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

Fuel starvation due to the pilot inadvertently shutting off its supply on approach for landing.



Montgomery Field Airport Approach / Landing: