20061211028169A

Accident · Substantial damage

FAA accident report · Piper PA-28-151 · Danbury, CT · December 11, 2006

Date
December 11, 2006 · 14:30 local
Place
Danbury, CT
Airport
Danbury Municipal
Phase of flight
Level Off Touchdown
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N44635
NTSB investigation
NTSBNYC07CA045
Reported as
Piper PA28151
Reported engine
Lycoming O320*
People aboard
1
Fatal injuries
0
Pilot’s certificate
Student
Pilot’s flight hours
17 total17 in this make and model17 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) As stated by the student pilot and the CFI observing the student pilot's first solo flight attempt on 12/11/2006. At approximately 14:00 hours the pilot privacy data omitted taxied to the control tower to let privacy data omitted (CFI) out of the aircraft. The CFI privacy data omitted would observe her from the control tower. The pilot privacy data omitted taxied to runway 35, departed normally, and flew a right hand pattern. The pilot privacy data omitted told the tower she intended a full stop on this landing. Her approach was fine; the landing was hard, the first contact with the runway knocked off her head set. The aircraft ballooned and the second hard contact with the runway broke off the nose wheel. The pilot privacy data omitted then executed a go around. The pilot privacy data omitted was instructed to climb to 1,700 feet, and stay in a right hand pattern to runway 35 until the airfield was cleared. After the third time around the pattern, the pilot privacy data omitted landed on runway 35 at 14:30 hours, and stopped prior to the runway intersection. The pilot privacy data omitted was not injured and egressed the aircraft on her own ability.

As the FAA filed it

(-23) AS STATED BY THE STUDENT PILOT AND THE CFI OBSERVING THE STUDENT PILOT'S FIRST SOLO FLIGHT ATTEMPT ON 12/11/2006. AT APPROXIMATELY 14:00 HOURS THE PILOT ^PRIVACY DAT^ TAXIED TO THE CONTROL TOWER TO LET ^PRIVACY DATA OMITTED^ (CFI) OUT OF THE AIRCRAFT. THE CFI ^PRIVACY DATA ^ WOULD OBSERVE HER FROM THE CONTROL TOWER. THE PILOT ^PRIVACY DAT^ TAXIED TO RUNWAY 35, DEPARTED NORMALLY, AND FLEW A RIGHT HAND PATTERN. THE PILOT ^PRIVACY DAT^ TOLD THE TOWER SHE INTENDED A FULL STOP ON THIS LANDING. HER APPROACH WAS FINE; THE LANDING WAS HARD, THE FIRST CONTACT WITH THE RUNWAY KNOCKED OFF HER HEAD SET. THE AIRCRAFT BALLOONED AND THE SECOND HARD CONTACT WITH THE RUNWAY BROKE OFF THE NOSE WHEEL. THE PILOT ^PRIVACY DAT^ THEN EXECUTED A GO AROUND. THE PILOT ^PRIVACY DAT^ WAS INSTRUCTED TO CLIMB TO 1,700 FEET, AND STAY IN A RIGHT HAND PATTERN TO RUNWAY 35 UNTIL THE AIRFIELD WAS CLEARED. AFTER THE THIRD TIME AROUND THE PATTERN, THE PILOT ^PRIVACY DAT^ LANDED ON RUNWAY 35 AT 14:30 HOURS, AND STOPPED PRIOR TO THE RUNWAY INTERSECTION. THE PILOT ^PRIVACY DAT^ WAS NOT INJURED AND EGRESSED THE AIRCRAFT ON HER OWN ABILITY.

NTSB investigation

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