OpenAirDocs.org

20120805019699I

Incident · Minor damage
Open the Markdown

FAA incident report · Piper PA-34-200 · Fort Lauderdale, FL · August 5, 2012

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
August 5, 2012 · 08:40 local
Place
Fort Lauderdale, FL
Airport
Fort Lauderdale Executive
Phase of flight
Maneuver
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N55223
Reported as
Piper PA-34-200
Reported engine
Lycoming I0360 series
People aboard
3
Fatal injuries
0
Other injuries
0
Pilot’s certificates
Airline transport, flight instructor
Pilot’s flight hours
11,450 total700 in this make and model150 in the last 90 days
N55223Registration cancelled Jan 30, 2021 · Piper PA-34-200S/N 34-7350188 · Built 1973Airframe modelPiper PA-34-200Engine modelLycoming I0360 seriesReciprocating

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 August 5, 2012, at 0840 EDT, aircraft N55223 returned to Fort Lauderdale Executive Airport (fxe) reporting a nose door problem, the aircraft landed without further incident. After contacting eastern air express (1EAA) it was reported that the aircraft was being operated under part 91 for the purpose of flight training with three persons on board (1 instructor, 1 student and 1 passenger). The flight instructor was privacy data omitted, holding a ATP and flight instructor ratings. The student was privacy data omitted, holding a private pilot single engine land and instrument ratings. The passenger was privacy data omitted, described as the girl friend of privacy data omitted privacy data omitted in a type written statement reported that after approximately 20 minutes into a training flight the nose cargo door opened while performing stall recoveries, they decided to return to alert the tower and return to fxe where they landed without incident and taxied back to hanger 42. privacy data omitted Reported that the preflight and take-off was normal. During a telephone conversation privacy data omitted stated that the baggage door was not opened during the preflight as there would not be a need to open it, he thought that there must have been a glitch in the key mechanism to allow the key to be removed without it being locked. privacy data omitted Stated that he performed his own walk around after privacy data omitted, he also stated that there was no indication that the door was going to open, ie a lifting of an edge, it just popped open possibly during the second stall recovery attempt. An examination of the door assembly and mechanisms did not reveal any defects other than the damage the door obtained while open in flight. The door was replaced with a serviceable door assembly and the lockset transferred from the removed door assembly to the serviceable door assembly. The aircraft was operated previously to and after this incident without any discrepancies with nose baggage door latching assemblies.

As the FAA filed it

ON AUGUST 5, 2012, AT 0840 EDT, AIRCRAFT N55223 RETURNED TO FORT LAUDERDALE EXECUTIVE AIRPORT (FXE) REPORTING A NOSE DOOR PROBLEM, THE AIRCRAFT LANDED WITHOUT FURTHER INCIDENT. AFTER CONTACTING EASTERN AIR EXPRESS (1EAA) IT WAS REPORTED THAT THE AIRCRAFT WAS BEING OPERATED UNDER PART 91 FOR THE PURPOSE OF FLIGHT TRAINING WITH THREE PERSONS ON BOARD (1 INSTRUCTOR, 1 STUDENT AND 1 PASSENGER). THE FLIGHT INSTRUCTOR WAS ^PRIVACY DATA OMITTED^, HOLDING A ATP AND FLIGHT INSTRUCTOR RATINGS. THE STUDENT WAS ^PRIVACY DATA OMITTED^, HOLDING A PRIVATE PILOT SINGLE ENGINE LAND AND INSTRUMENT RATINGS. THE PASSENGER WAS ^PRIVACY DATA OMITTED^, DESCRIBED AS THE GIRL FRIEND OF ^PRIVACY DATA OMITTED^ ^PRIVACY DATA OMITTED^ IN A TYPE WRITTEN STATEMENT REPORTED THAT AFTER APPROXIMATELY 20 MINUTES INTO A TRAINING FLIGHT THE NOSE CARGO DOOR OPENED WHILE PERFORMING STALL RECOVERIES, THEY DECIDED TO RETURN TO ALERT THE TOWER AND RETURN TO FXE WHERE THEY LANDED WITHOUT INCIDENT AND TAXIED BACK TO HANGER 42. ^PRIVACY DATA OMITTED^ REPORTED THAT THE PREFLIGHT AND TAKE-OFF WAS NORMAL. DURING A TELEPHONE CONVERSATION ^PRIVACY DATA OMITTED^ STATED THAT THE BAGGAGE DOOR WAS NOT OPENED DURING THE PREFLIGHT AS THERE WOULD NOT BE A NEED TO OPEN IT, HE THOUGHT THAT THERE MUST HAVE BEEN A GLITCH IN THE KEY MECHANISM TO ALLOW THE KEY TO BE REMOVED WITHOUT IT BEING LOCKED. ^PRIVACY DATA OMITTED^ STATED THAT HE PERFORMED HIS OWN WALK AROUND AFTER ^PRIVACY DATA OMITTED^, HE ALSO STATED THAT THERE WAS NO INDICATION THAT THE DOOR WAS GOING TO OPEN, IE A LIFTING OF AN EDGE, IT JUST POPPED OPEN POSSIBLY DURING THE SECOND STALL RECOVERY ATTEMPT.AN EXAMINATION OF THE DOOR ASSEMBLY AND MECHANISMS DID NOT REVEAL ANY DEFECTS OTHER THAN THE DAMAGE THE DOOR OBTAINED WHILE OPEN IN FLIGHT. THE DOOR WAS REPLACED WITH A SERVICEABLE DOOR ASSEMBLY AND THE LOCKSET TRANSFERRED FROM THE REMOVED DOOR ASSEMBLY TO THE SERVICEABLE DOOR ASSEMBLY. THE AIRCRAFT WAS OPERATED PREVIOUSLY TO AND AFTER THIS INCIDENT WITHOUT ANY DISCREPANCIES WITH NOSE BAGGAGE DOOR LATCHING ASSEMBLIES.