20110925025189A

Accident · Substantial damage

FAA accident report · Cessna 172S · Phoenix, AZ · September 25, 2011

Date
September 25, 2011 · 19:20 local
Place
Phoenix, AZ
Airport
Deer Valley Municipal Airport
Phase of flight
Landing: Touchdown
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N169ME
NTSB investigation
NTSBWPR11CA466
Reported as
Cessna 172S
Reported engine
Lycoming I0360 series
People aboard
2
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Commercial pilot
Pilot’s flight hours
383 total320 in this make and model55 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.

On 09/25/11, privacy data omitted was acting as a safety pilot for privacy data omitted on a part 91 flight from kvgt to kdvt. As they approached kdvt, the sun had already set, and privacy data omitted expressed discomfort at landing in semi-darkness. privacy data omitted Asked privacy data omitted if he could take controls for the landing, since she was uncomfortable. Sunset was at 1821 MST; the landing occurred at 1920 MST. Neither pilot was current for night landings. privacy data omitted Was sitting in the right seat and had landed from the right seat only once previously. Both pilots stated that privacy data omitted approach was on glidepath and stabilized. Both pilots stated that privacy data omitted touched down slightly right of centerline. The winds at the time were approximately 230 @ 11 knots. privacy data omitted Then lost directional control on the landing at kdvt runway 25L. He exited the right side of the runway, crossed taxiway bravo, and came to rest with the nose gear sheared off between taxiway bravo and runway 25R at 1920 MST. privacy data omitted Takes full responsibility for the landing and subsequent aircraft damage. On 09/30/2011, counseling was provided to both privacy data omitted and privacy data omitted. Subjects addressed included: performing a personal assessment of night currency/comfort with flying close to sunset, a discussion of what pilot in command means, and the importance of establishing and maintaining pilot in command, and knowing at all times who is pilot in command.

As the FAA filed it

ON 09/25/11, ^PRIVACY DATA OMITTED^ WAS ACTING AS A SAFETY PILOT FOR ^PRIVACY DATA OMITTED^ ON A PART 91 FLIGHT FROM KVGT TO KDVT. AS THEY APPROACHED KDVT, THE SUN HAD ALREADY SET, AND ^PRIVACY DATA OMITTED^ EXPRESSED DISCOMFORT AT LANDING IN SEMI-DARKNESS. ^PRIVACY DATA OMITTED^ ASKED ^PRIVACY DATA OMITTED^ IF HE COULD TAKE CONTROLS FOR THE LANDING, SINCE SHE WAS UNCOMFORTABLE. SUNSET WAS AT 1821 MST; THE LANDING OCCURRED AT 1920 MST. NEITHER PILOT WAS CURRENT FOR NIGHT LANDINGS. ^PRIVACY DATA OMITTED^ WAS SITTING IN THE RIGHT SEAT AND HAD LANDED FROM THE RIGHT SEAT ONLY ONCE PREVIOUSLY. BOTH PILOTS STATED THAT ^PRIVACY DATA OMITTED^ APPROACH WAS ON GLIDEPATH AND STABILIZED. BOTH PILOTS STATED THAT ^PRIVACY DATA OMITTED^ TOUCHED DOWN SLIGHTLY RIGHT OF CENTERLINE. THE WINDS AT THE TIME WERE APPROXIMATELY 230 @ 11 KNOTS. ^PRIVACY DATA OMITTED^ THEN LOST DIRECTIONAL CONTROL ON THE LANDING AT KDVT RUNWAY 25L. HE EXITED THE RIGHT SIDE OF THE RUNWAY, CROSSED TAXIWAY BRAVO, AND CAME TO REST WITH THE NOSE GEAR SHEARED OFF BETWEEN TAXIWAY BRAVO AND RUNWAY 25R AT 1920 MST. ^PRIVACY DATA OMITTED^ TAKES FULL RESPONSIBILITY FOR THE LANDING AND SUBSEQUENT AIRCRAFT DAMAGE. ON 09/30/2011, COUNSELING WAS PROVIDED TO BOTH ^PRIVACY DATA OMITTED^ AND ^PRIVACY DATA OMITTED^. SUBJECTS ADDRESSED INCLUDED: PERFORMING A PERSONAL ASSESSMENT OF NIGHT CURRENCY/COMFORT WITH FLYING CLOSE TO SUNSET, A DISCUSSION OF WHAT PILOT IN COMMAND MEANS, AND THE IMPORTANCE OF ESTABLISHING AND MAINTAINING PILOT IN COMMAND, AND KNOWING AT ALL TIMES WHO IS PILOT IN COMMAND.

NTSB investigation

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