# NTSB IAD00LA060: Piper PA-32-300, N21072, Fitchburg, MA, July 8, 2000

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: July 8, 2000, 10:00 local (14:00 UTC)
- Place: Fitchburg, MA
- Location: 42.5538° N, 71.7592° W: Placed by OpenAirDocs at FITCHBURG MUNI (FIT), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=42.5538&lon=-71.7592&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report December 18, 2001
- Report: Approved by Office Director
- NTSB case key (mKey): 49667
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=IAD00LA060
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/49667/pdf
- Page: https://openairdocs.org/ntsb/IAD00LA060

## Probable cause

pilot's inadequate compensation for the crosswind.  A factor was the crosswind.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of control - on ground/water, landing - roll
  - weather condition - crosswind (contributing factor)
  - compensation for wind conditions - inadequate, pilot in command (cause)
- On ground/water encounter with terrain/water, landing - roll

## Analysis

Before entering the airport's traffic pattern, the pilot tuned into the airport's ASOS and was informed that the winds were favoring Runway 02.  The pilot observed traffic in the pattern utilizing Runway 32, and made a 45 degree entry to the downwind for Runway 32.  He flew a normal traffic pattern and set up for a crosswind landing.  On the landing roll-out, the airplane drifted to the left of the runway centerline, then veered right, and exited the runway onto the grass.  The nose gear then sheered off the airplane, which resulted in damage to the firewall and propeller. Examination of the airplane revealed there were no mechanical malfunctions.  The airport's reported winds were from 020 degrees at 12 knots.

## Factual narrative

On July 8, 2000, at 1000 Eastern Daylight Time, a Piper PA-32-300, N21072, was substantially damaged during landing roll-out at Fitchburg Municipal Airport (FIT), Fitchburg, Massachusetts.  The certificated private pilot/owner was not injured.  Visual meteorological conditions prevailed and no flight plan was filed for the personal flight conducted under 14 CFR part 91.

In a written statement, the pilot said:

"I left Fitchburg airport at 0730 am to use [the] auto pilot [to track] VORs.  At around 0930 I noticed that my alternator light was on and [the] amp meter was reading 0 amps.  I decided to track back to Fitchburg.  Upon arriving at the airport, I dialed in ASOS on the radio.  The winds were favoring runway 02, but I noticed that airplane traffic was using [runway] 32.  I set up my 45 degree entry to the downwind for runway 32.  On short final on [runway] 32, I set up for [a] cross wind landing.   On touchdown, my nose wheel started to veer to the right into the wind.  I tried to straighten the nose wheel, but could not.  At that point I knew that I was heading off the runway to the grass.  I shut off the engine with the ignition switch."

Another pilot was flying in the FIT traffic pattern and observed N21072.  In a written statement, he said:

"N21072 entered left downwind in front of me.  [The] approach seemed normal.  [The airplane] touchdown on centerline, started to drift to the left, and then skidded off the right side of the runway.  The winds were 010-330 degrees, 7-8 knots."

A Federal Aviation Administration (FAA) inspector performed and on scene examination on July 8, 2000.  According to the inspector, the nose gear had separated from the airplane, and the propeller and firewall were damaged.

On June 25, 2000, the pilot received a high-performance-airplane endorsement in N21072 from an FAA certified flight instructor. The pilot reported 150 total flight hours, of which 40 hours were in make and model.

The pilot also reported there were no mechanical malfunctions.

The airport's reported winds at 0952 were from 020 degrees at 12 knots.

## Aircraft

- Registration: [N21072](https://openairdocs.org/deregistered/N21072-2004-09-15), registration cancelled 2004-09-15, S/N 32-7840183, built 1978 (OpenAirDocs)
- Reported make and model: Piper PA-32-300
- Registry model: [Piper PA-32-300](https://openairdocs.org/model/piper-pa-32-300) (registry code 7103212) (OpenAirDocs)
- Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 37-7840183
- Airframe hours: 2693
- Engines: Lycoming I0-540-K1G5 300 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: James P. Normandin
- Airworthiness certificate: Standard, Normal
- Departed: FIT
- Airport: FIT, Fitchburg Municipal, runway 32, 4,511 × 100 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 43; private; airplane ratings: single-engine land; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 150 total, 40 in this make and model, 11 as pilot in command, 50 in the last 90 days, 10 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 20° at 12 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 66 °F, dew point 46 °F
- Altimeter: 30.00 inHg
- Observed at: FIT

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20000708041269A](https://openairdocs.org/incident/20000708041269A), Jul 8, 2000: Piper PA32300, Fitchburg, MA, Substantial damage. (.4) Before entering the airport's traffic pattern, the pilot tuned into the airport's ASOS and was informed that the winds were favoring runway 02. The pilot…

## Other investigations on N21072 (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 NYC04FA136](https://openairdocs.org/ntsb/NYC04FA136), Jun 2, 2004: Piper PA-32-300 (N21072), Leominster, MA, destroyed, 2 fatal. Probable cause: The pilot's failure to follow instrument flight procedures resulting in a collision with trees. A factor related to the accident was the low cloud ceiling, and dark night.

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.

---
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.
