FTW97LA214

NTSB accident investigation · Piper PA-34-200T · Santa Teresa, NM · May 30, 1997

Accident · No injuriesLimited investigationFinal report
Date
May 30, 1997, 09:24 local (15:24 UTC)
Place
Santa Teresa, NM
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N36275Piper PA-34-200T
Weather
Visual (VMC) · Day
Status
Completed · report December 15, 1997
Report
Approved by Office Director
FAA report
19970530013979A
Case key
20237

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

the pilot-in-command's (PIC's) inadequate supervision of the flight by allowing the pilot-rated passenger to attempt a go-around (aborted landing) without maitaining minimum control speed (VMC), which resulted in loss of aircraft control. Factors relating to the accident were: the pilot-rated passenger's improper flare and improper recovery from a bounced landing.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Hard landingLanding - flare/touchdown
Flare - improperPilot passengerFactor
Recovery from bounced landing - improperPilot passengerFactor
Loss of control - on ground/waterLanding - aborted
Go-around - attemptedPilot passenger
Supervision - inadequatePilot in commandCause
Airspeed(vmc) - not maintainedPilot in commandCause
Aircraft control - not maintainedPilot in commandCause

Analysis

Witnesses at the airport observed the airplane entering the traffic pattern for touch-and-go landings on runway 28. They reported that the airplane landed hard, porpoised 3 or 4 times, and departed the right side of the runway. According to the pilot-in-command (PIC), the pilot rated passenger in the right seat, who was reported to hold an airline transport rating, applied full power after announcing 'lets go around.' The power in the right engine 'was slow to develope, which instantly skewed the airplane off the runway.' The PIC stated that the airplane was at about 5 feet off the ground as 'he reduced the power to the good engine.' The PIC added that the airspeed was at or near VMC, and 'the airplane started to roll and directional control was not possible.' The PIC reported that he 'pulled both engines back and flared.' In the recommendation block of a Pilot/Operator Report, the PIC recommended 'not attempting [a] full throttle go-around until both engines are confirmed operational, or far above VMC.'

Factual narrative

On May 30, 1997, at 0924 mountain daylight time, a Piper PA-34-200T twin engine airplane, N36275, was substantially damaged following a loss of control while landing at the Santa Teresa Municipal Airport, near Santa Teresa, New Mexico. The airline transport rated pilot and his two passengers were not injured. The airplane, owned and operated by a private individual, was being operated under Title 14 CFR Part 91. Visual meteorological conditions prevailed for the personal flight for which a flight plan was not filed. The local flight originated from Santa Teresa at 0900.

The pilot-in-command (PIC) stated that the purpose of the flight was to verify engine performance of the left engine. The engine cooling baffles on the left engine had been recently replaced by the new owner of the airplane who purchased the airplane on April 23, 1997.

According to witnesses at the airport, the airplane was observed entering the traffic pattern for touch and go landings on runway 28. Witnesses reported that the airplane landed hard, porpoised 3 or 4 times, and departed the right side of the runway. The right wing struck the ground resulting in structural damage to the airplane.

According to the PIC, the pilot rated passenger in the right front seat, who was reported to hold an airline transport rating, applied full power after announcing "lets go around." The PIC added that the power on the right engine "was slow to come up instantly skewing the airplane off the runway." The PIC further stated that the airplane was at approximately 5 feet off the ground as "he reduced the power to the good engine." The PIC added that the airspeed was at or near VMC and the airplane "started to roll and directional control was not possible." The PIC added that he "pulled both engines back and flared" the airplane.

On the recommendation block of the enclosed Pilot/Operator Report, in order to prevent the accident, the PIC recommended "not attempting [a] full throttle go-around until both engines are confirmed operational, or far above VMC."

The name of the passenger seated in the back seat was never determined. The investigator-in-charge (IIC) was able to conduct a brief telephonic interview with the PIC the day after the accident; however, the PIC never returned any subsequent phone calls. A telephone number was not provided for the pilot rated passenger in the right seat and his wife, who is the registered owner of the airplane.

Aircraft

Registration
N36275
Reported as
Piper PA-34-200T
Category
Airplane
Serial number
34-7870308
Engine
Continental TSIO-360, 210 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Latrenda D. Hossler
Airworthiness certificate
Standard, Normal
Departed
5T6
Airport
5T6 · Dona Ana County, runway 28, 8,500 × 100 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
54
Certificate
Airline transport
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 2, Valid Medical--w/ waivers/lim
Seat
Left
Flight hours
5,755 total · 59 in this make and model · 5,498 as pilot in command · 51 in the last 90 days · 37 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
250° at 4 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
82 °F, dew point 37 °F
Altimeter
30.00 inHg
Observed at
ELP, 25 nm away

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.