20080718848649I

Incident · No damage

FAA incident report · Piper PA-44-180 · Las Vegas, NV · July 18, 2008

Date
July 18, 2008 · 11:44 local
Place
Las Vegas, NV
Phase of flight
Normal Cruise
Operating rules
General operating rules (Part 91)
Damage
No damage
Aircraft
N118AT
Reported as
Piper PA44180
People aboard
2
Fatal injuries
0
Pilot’s flight hours
170 total85 in this make and model100 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.

(-23) N118AT was on an IFR flight cruising at an assigned altitude of 12,000 feet en route to the north Las Vegas air terminal when la center issued to traffic advisory at 12 o'clock, 2 miles, opposite direction 1,000 feet below. Several seconds later, center queried N118AT about its altitude because of an altitude alert issued by the ATC automation. N118AT replied he was fighting a little turbulence, but was back level at 12,000 feet. Ntap shows the airplane descended 400 feet below it assigned altitude resulting in a loss of separation from opposite direction traffic at 11,000 feet. This was a brief and limited excursion from the assigned altitude. It appears the pilot may have been distracted looking from traffic below just after the traffic advisory and allowed the aircraft to descend. He was also dealing with turbulence. However, it appears that the turbulence experienced was not severe enough to exceed the pilot's or aircraft's capability of maintaining altitude, but we cannot prove this to be the case. With more careful attention, the pilot probably could have employed flight control inputs to compensate for turbulence and maintain the assigned altitude. I contacted the pilot by phone 8/7 & 8/8/2008 and counseled him.

As the FAA filed it

(-23) N118AT WAS ON AN IFR FLIGHT CRUISING AT AN ASSIGNED ALTITUDE OF 12,000 FEET EN ROUTE TO THE NORTH LAS VEGAS AIR TERMINAL WHEN LA CENTER ISSUED TO TRAFFIC ADVISORY AT 12 O'CLOCK, 2 MILES, OPPOSITE DIRECTION 1,000 FEET BELOW. SEVERAL SECONDS LATER, CENTER QUERIED N118AT ABOUT ITS ALTITUDE BECAUSE OF AN ALTITUDE ALERT ISSUED BY THE ATC AUTOMATION. N118AT REPLIED HE WAS FIGHTING A LITTLE TURBULENCE, BUT WAS BACK LEVEL AT 12,000 FEET. NTAP SHOWS THE AIRPLANE DESCENDED 400 FEET BELOW IT ASSIGNED ALTITUDE RESULTING IN A LOSS OF SEPARATION FROM OPPOSITE DIRECTION TRAFFIC AT 11,000 FEET. THIS WAS A BRIEF AND LIMITED EXCURSION FROM THE ASSIGNED ALTITUDE. IT APPEARS THE PILOT MAY HAVE BEEN DISTRACTED LOOKING FROM TRAFFIC BELOW JUST AFTER THE TRAFFIC ADVISORY AND ALLOWED THE AIRCRAFT TO DESCEND. HE WAS ALSO DEALING WITH TURBULENCE. HOWEVER, IT APPEARS THAT THE TURBULENCE EXPERIENCED WAS NOT SEVERE ENOUGH TO EXCEED THE PILOT'S OR AIRCRAFT'S CAPABILITY OF MAINTAINING ALTITUDE, BUT WE CANNOT PROVE THIS TO BE THE CASE. WITH MORE CAREFUL ATTENTION, THE PILOT PROBABLY COULD HAVE EMPLOYED FLIGHT CONTROL INPUTS TO COMPENSATE FOR TURBULENCE AND MAINTAIN THE ASSIGNED ALTITUDE. I CONTACTED THE PILOT BY PHONE 8/7 & 8/8/2008 AND COUNSELED HIM.