# Incident 20130709017229I: Cessna 421C, Beverly, MA, July 9, 2013

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 9, 2013, 11:29 local time
- Place: Beverly, MA
- Airport: Beverly Municipal Airport
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 42.5841° N, 70.9161° W: Placed by OpenAirDocs at BEVERLY RGNL (BVY), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=42.5841&lon=-70.9161&mi=10
- Aircraft: N2740B, a cancelled registration (https://openairdocs.org/deregistered/N2740B-2018-08-20) (OpenAirDocs)
- Registry model: Cessna 421C (registry code 2076016, https://openairdocs.org/model/cessna-421c) (OpenAirDocs)
- Registry engine: Continental GTSIO-520 series (registry code 17039, https://openairdocs.org/engine/continental-gtsio-520-series) (OpenAirDocs)
- Reported make and model: CESSNA 421C
- Reported engine: CONT MOTOR GTSIO-520 SER
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 647 total, 55 in this make and model, 65 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130709017229I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON JULY 9, 2013, N 2740B EXECUTED THE RUNWAY 16 GPS APPROACH AT THE KBVY(BEVERLY MUNICIPAL AIRPORT).  THE APPROACH TERMINATED IN A LANDING ON RUNWAY 16.  AT SOME POINT DURING THE LANDING, BOTH MAIN TIRES FAILED (BLOWN) CAUSING DAMAGE TO THE LEFT MAIN WHEEL AS WELL AS THE LEFT BRAKE DISC.

THE PIC ELECTED TO TAXI THE AIRCRAFT CLEAR OF THE RUNWAY NOTING THAT CONSIDERABLE POWER WAS REQUIRED TO ACTUALLY MOVE THE AIRCRAFT.  UPON REALIZING THAT FURTHER TAXI WAS NOT FEASIBLE, THE AIRCRAFT WAS STOPPED AND SHUT DOWN ON THE RUN UP AREA ADJACENT TO THE APPROACH END OF RUNWAY 34.

NORTH ATLANTIC AVIATION MAINTENANCE PERSONNEL RESPONDED TO THE DISABLED AIRCRAFT.  THE AIRCRAFT WAS JACKED AND BOTH MAIN WHEELS WERE REMOVED.  TEMPORARY TIRES WERE INSTALLED ON THE AIRCRAFT'S RIMS.  THE TEMPORARY WHEEL ASSEMBLIES WERE RE-INSTALLED ONTO THE DISABLED AIRCRAFT ALLOWING THE AIRCRAFT TO BE RELOCATED TO THE NORTH ATLANTIC AVIATION RAMP.

A BOSTON FSDO INSPECTOR RESPONDED TO THE INCIDENT WITHIN 1 HOUR OF BEING NOTIFIED.  UPON ARRIVAL, BOTH MAIN TIRES WERE FOUND TO BE REMOVED FROM THE AIRCRAFT'S RIMS AND IN A FAILED (BLOWN OUT) CONDITION.  THE RIGHT MAIN WHEEL ASSEMBLY SHOWED NO VISIBLE DAMAGE AND NORTH ATLANTIC AVIATION MAINTENANCE PERSONNEL STATED THAT THE RIM ITSELF APPEARED TO BE IN A SERVICABLE CONDITION.  THE LEFT MAIN WHEEL EXHIBITED DAMAGE TO BOTH THE RIM AS WELL AS THE BRAKE DISC.  THE DAMAGE WAS CONSISTENT WITH CONTACT WITH THE RUNWAY SURFACE AT SPEED, FOR A CONSIDERABLE DISTANCE.

A CURSORY INSPECTION OF THE WING UNDER SURFACE AND AIRCRAFT VENTRAL SURFACE WAS CONDUCTED.  NO DAMAGE WAS APPARENT.

THE PIC WAS INTERVIEWED.  THE PIC STATED THAT AFTER HE EXECUTED THE GPS APPROACH TO RUNWAY 16 HE OBTAINED VISUAL CONTACT WITH THE RUNWAY OF INTENDED USE ABOUT THREE MILES FROM THE AIRPORT.  THE PILOT DESCRIBED HIS APPROACH TO LANDING AS NORMAL.  THE PILOT STATED THAT APPROACH SPEED WAS NORMAL AND THAT HIS TOUCH DOWN WAS WITHIN THE FIRST THIRD OF THE RUNWAY.  THE PIC DESCRIBED HIS BRAKING EFFORTS AS OVERLY AGGRESSIVE AND IDENTIFIED HIS OVERLY AGGRESSIVE BRAKING INPUT AS THE CAUSE OF THE TIRE FAILURE.

NORTH ATLANTIC AVIATION MAINTENANCE PERSONNEL STATED THAT THE SKID MARKS RESULTING FROM THIS INCIDENT BEGAN AT A POINT APPROXIMATELY ONE HUNDRED YARDS NORTH WEST OF TAXIWAY ALPHA.  THE APPROXIMATE DISTANCE WAS PLOTTED ON A GOOGLE EARTH IMAGE USING THE MEASURING TOOL.  IT WAS DETERMINED THAT THE SKID MARKS BEGAN A CONSIDERABLE DISTANCE OUTSIDE OF THE THOUCH DOWN ZONE OF RUNWAY 16.

DURING THE INTERVIEW, THE PIC STATED THAT HE HAD ATTENDED SIM COM TRAINING FOR MAKE AND MODEL AND HAS ACCUMULATED APPROXIMATELY 60 HOURS OF PILOT TIME IN THE AIRCRAFT.

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.
