# Incident 20160730012639I: Bellanca 17-30A, North Andover, MA, July 30, 2016 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: July 30, 2016, 07:23 local time - Place: North Andover, MA - Airport: Lawrence Municipal - Damage: Minor damage - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Location: 42.7170° N, 71.1235° W: Placed by OpenAirDocs at LAWRENCE MUNI (LWM), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=42.7170&lon=-71.1235&mi=10 - Aircraft: N666RS, registered now (https://openairdocs.org/aircraft/N666RS) (OpenAirDocs) - Registry model: Bellanca 17-30A (registry code 1220433, https://openairdocs.org/model/bellanca-17-30a) (OpenAirDocs) - Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs) - Reported make and model: BELLANCA 17-30A - People aboard: 2 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Private pilot - Pilot flight hours: 364 total - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20160730012639I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON JULY 30, 2016, ABOUT 0723 EASTERN DAYLIGHT TIME, A BELLANCA, 17-30A, N666RS, SUSTAINED MINOR DAMAGE DURING A NOSE LANDING GEAR COLLAPSE ON TOUCHDOWN AT LAWRENCE MUNICIPAL AIRPORT (LWM), NORTH ANDOVER, MASSACHUSETTS. THE PRIVATE PILOT AND PASSENGER ONBOARD WERE NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED, AND NO FLIGHT PLAN WAS FILED FOR THE PERSONAL FLIGHT, WHICH WAS OPERATED UNDER THE PROVISIONS OF TITLE 14 CODE OF FEDERAL REGULATIONS PART 91. THE PILOT PROVIDED A WRITTEN STATEMENT, WHICH WAS SUPPORTED BY AIR TRAFFIC CONTROL (ATC) VOICE RECORDS. THE PILOT WAS CLEARED TO LAND RUNWAY 32 AND INFORMED ATC THAT HE WAS HAVING A GREEN LIGHT PROBLEM WITH HIS GEAR AND REQUESTED TO GO-AROUND. ATC ASKED THE PILOT IF HE WANTED TO MAKE A LOW APPROACH IN ORDER TO TAKE A LOOK AT THE LANDING GEAR. THE PILOT PROCEEDED TO MAKE A LOW APPROACH OVER RUNWAY 32 AT APPROXIMATELY 200 FEET MEAN SEA LEVEL (MSL). ATC INFORMED THE PILOT THAT HIS LANDING GEAR APPEARS TO BE NORMAL. ATC ASKED THE PILOT FOR HIS INTENTIONS AND THE PILOT REQUESTED A FULL STOP LANDING. THE PILOT WAS CLEARED TO LAND RUNWAY 32 WITH WINDS REPORTING 320 AT 7 KNOTS. WHILE FLYING IN THE TRAFFIC PATTERN, THE PILOT PERFORMED THE LANDING GEAR EMERGENCY EXTENSION PROCEDURE, WHICH INCLUDED REDUCING THE AIRSPEED TO 85 MILES PER HOUR (MPH) AND PUSHING DOWN ON THE EMERGENCY GEAR EXTENSION LEVER. PHOTOGRAPHS TAKEN OF THE AIRCRAFT AFTER THE INCIDENT CONFIRMED ACTUATION OF THE EMERGENCY GEAR EXTENSION LEVER. HOWEVER, THE NOSE LANDING GEAR GREEN GEAR DOWN INDICATOR LIGHT DID NOT ILLUMINATE FOLLOWING THE PERFORMANCE OF THE LANDING GEAR EMERGENCY EXTENSION PROCEDURE. THE PILOT ELECTED TO CONTINUE WITH THE FULL STOP LANDING. THE PILOT LANDED ON RUNWAY 32 AND MAINTAINED A NOSE HIGH ATTITUDE. AS THE NOSE LANDING GEAR TOUCHED THE PAVED SURFACE THE PILOT REPORTED THAT HE FELT IT SOFTEN AND WAS UNAWARE IF THE PROPELLER BLADES HAD MADE CONTACT WITH THE PAVED SURFACE. THE PILOT THEN INCREASED THE THROTTLE MOMENTARILY BEFORE DECIDING TO REDUCE ALL POWER AFTER MAKING THE DETERMINATION THAT IF THE PROPELLER BLADES HAD IN FACT STRUCK THE PAVED SURFACE HE WOULD BE FURTHER ENDANGERING OTHERS. THESE REMARKS ARE SUPPORTED BY THE MARKINGS OBSERVED ON RUNWAY 32. THE PROPELLER STRIKE MARKS AND UPPER NOSE LANDING GEAR DOOR SCRAPE MARKS BEGIN APPROXIMATELY 527 FEET FROM THE RUNWAY THRESHOLD AND DISAPPEAR APPROXIMATELY 652 FEET FROM THE RUNWAY THRESHOLD. THE UPPER AND LOWER NOSE LANDING GEAR DOOR SCRAPE MARKS REAPPEAR PROMINENTLY APPROXIMATELY 1137 FEET FROM THE RUNWAY THRESHOLD AND CONTINUE TO APPROXIMATELY 1423 FEET FROM THE RUNWAY THRESHOLD ON THE RIGHT EDGE, WHICH IS WHERE THE AIRCRAFT CAME TO REST. THE PILOT SECURED THE AIRPLANE AND THE PILOT AND PASSENGER EGRESSED ON THE RUNWAY. 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.