# Accident 20130318003459A: Piper PA-23-250, Hillsboro, OR, March 18, 2013 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: March 18, 2013, 14:15 local time - Place: Hillsboro, OR - Airport: Twin Oaks Airpark - Damage: Substantial damage - Phase of flight: Takeoff: Departure Roll - Operating rules: General operating rules (Part 91) - Location: 45.4256° N, 122.9453° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=45.4256&lon=-122.9453&mi=10 - Aircraft: N318CA, a cancelled registration (https://openairdocs.org/deregistered/N318CA-2014-09-05) (OpenAirDocs) - Registry model: Piper PA-23-250 (registry code 7102308, https://openairdocs.org/model/piper-pa-23-250) (OpenAirDocs) - Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs) - Reported make and model: PIPER PA-23-250 - Reported engine: LYCOMING TI0-540 SER - People aboard: 2 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Airline transport, flight instructor - Pilot flight hours: 9,368 total, 5 in this make and model, 66 in the last 90 days - NTSB investigation: [NTSB WPR13LA154](https://openairdocs.org/ntsb/WPR13LA154) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20130318003459A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON MARCH 18, 2013, AT APPROXIMATELY 14:30 (2130 Z), A PIPER AZTEC PA-23-250, N318CA, WENT OFF THE END OF RUNWAY 20 AT TWIN OAKS AIRPARK IN HILLSBORO, OR. THIS FLIGHT WAS TO BE THE STUDENT PRIVATE PILOT?S FIRST TRAINING FLIGHT IN A TWIN ENGINE AIRCRAFT. HIS FLIGHT INSTRUCTOR PERFORMED A PRE-FLIGHT SAFETY BRIEF INCLUDING ENGINE FAILURE AND PROCEDURES SHOULD THE DOOR BECOME UNSECURE DURING THE TAKE-OFF ROLL. NORMAL ENGINE RUN UPS AND TAXI TO RUNWAY 20, INCLUDING A BRAKE FUNCTION CHECK, WERE PERFORMED, WITH NO DISCREPANCIES NOTED. THE TAKE-OFF PROCEEDED NORMALLY UNTIL THE CABIN DOOR BECAME UNLATCHED AT APPROXIMATELY 1/3 DOWN THE RUNWAY, BY CFI?S RECOLLECTION, AND BETWEEN 80 AND 85 MILES PER HOUR, AT WHICH TIME SHE CALLED ?ABORT?. THE STUDENT PILOT IMMEDIATELY PULLED THE POWER OFF AND BEGAN BRAKING. THE RUNWAY LENGTH FROM THRESHOLD TO THRESHOLD IS 2225 FEET. WITNESSES DESCRIBED HEARING THE POWER COME OFF AND TURNING TO LOOK AT THE AIRCRAFT AS IT BEGAN BRAKING. THEY DESCRIBED THE LOCATION OF THE AIRCRAFT AS APPROXIMATELY 700-800 FEET DOWN THE RUNWAY AT THAT TIME, WITH APPROXIMATELY 1400-1500 FEET REMAINING TO THE BEGINNING OF THE OVER-RUN. THE ENTIRE RUNWAY 20 IS DOWNHILL, 151 FEET ELEVATION TO 141 FEET ELEVATION, THRESHOLD TO THRESHOLD. FROM BEGINNING OF THE SOUTHERN OVERRUN, IT IS EVEN MORE PRONOUNCED. 141 FEET ELEVATION TO 115 IN A DISTANCE OF ONLY 171 FEET, TO THE END OF THE HARD TOP. (DISTANCE AND ELEVATION DATA DERIVED FROM GOOGLE EARTH). STUDENT PILOT STATED THAT HE WAS ?STANDING ON? THE BRAKES (THERE ARE NO BRAKE PEDALS ON THE RIGHT SIDE AT CFI?S CREW POSITION). HE FELT THAT THE BRAKES WERE EFFECTIVE AT THE BEGINNING OF THE DE-ACCELERATION, BUT FELT EFFECTIVENESS FADE THE LONGER HE APPLIED THEM. BRAKE FADE WOULD BE TYPICAL AS THE BRAKES BEGAN TO OVERHEAT. VISUAL INSPECTION OF THE BRAKE ASSEMBLIES POST ACCIDENT REVEILLED NO ANOMILALIES. NO ATTEMPT WAS MADE TO TURN . ONE WITNESS STATED THAT IT APPEARED THAT THE BRAKES NEVER ?LOCKED UP? AND NO SKID MARKS THAT COULD BE ATTRIBUTED TO THE ACCIDENT WERE NOTED. ONCE THE AIRCRAFT LEFT THE BLACK TOP, IT DROPPED OFF A TEN FOOT SLOPED EMBANKMENT, COMING TO REST APPROXIMATELY 57 FEET OFF THE BLACK TOP. THE AIRCRAFT WAS SUBSTANTIALLY DAMAGED. DAMAGE TO THE AIRCRAFT INCLUDED ALL THREE LANDING GEAR LEGS FOLDED OR BENT AFT, THE NOSE WHEEL BAY WAS CRUSHED, BOTH WINGS WERE BENT FORWARD AND THE TRAINING EDGES PULLED AWAY FROM THE FUSELAGE. THE FUSELAGE WAS WRINKLED AT THE FORWARD SPAR ATTACH POINT. BOTH PROPELLERS HAD ONE BENT BLADE. ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB WPR13LA154](https://openairdocs.org/ntsb/WPR13LA154), Mar 18, 2013: Piper PA-23-250 (N318CA), Hillsboro, OR, substantial damage. Probable cause: A runway overrun due to an insufficient stopping distance due to the downsloping runway during a rejected takeoff. Contributing to the accident was a cabin door that inadvertently opened during the… ## Other reports on N318CA (1) Matched to the same aircraft by N-number and date. - [Incident 20120529010719I](https://openairdocs.org/incident/20120529010719I), May 29, 2012: Piper PA-23-250 (N318CA), Mcminnville, OR, Minor damage. Aircraft departed twin oaks airpark (7S3) for an instructional flight. While on final approach into mmv, with the left engine simulated out for training… From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.