# NTSB NYC00LA252: Piper PA-60-601P, N601WK, Northampton, MA, September 7, 2000

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: September 7, 2000, 07:55 local (11:55 UTC)
- Place: Northampton, MA
- Location: 42.3280° N, 72.6112° W: Placed by OpenAirDocs at NORTHAMPTON (7B2), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=42.3280&lon=-72.6112&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report July 2, 2001
- Report: Approved by Office Director
- NTSB case key (mKey): 50227
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC00LA252
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/50227/pdf
- Page: https://openairdocs.org/ntsb/NYC00LA252

## Probable cause

The pilot's improper preflight planning which resulted in an attempted takeoff from a taxiway.  A factor in the accident was the fog.

## Sequence of events

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

- On ground/water collision with object, takeoff - aborted
  - object - tree(s)
  - preflight planning/preparation - improper, pilot in command (cause)
  - weather condition - fog (contributing factor)

## Analysis

The airport consisted of a single runway oriented on a heading of 140/320 degrees.  A taxiway oriented on a 120 degree heading intersected the runway at its midpoint.  The pilot reported that the visibility was 500-1,000 feet with fog at the time of departure.  Before he took off, the pilot asked his passenger to walk the length of the runway to observe any obstructions, due to the reduced visibility.  The pilot then taxied to the run-up pad, set the heading of his HSI to 120 degrees, and initiated the takeoff.  When the airspeed reached 80 knots, the pilot realized he had initiated the takeoff on the taxiway instead of the runway.  He aborted the takeoff and attempted to maneuver the airplane to the runway.  The airplane crossed the runway, impacted a tree, and came to rest upright in a cornfield.  The weather reported at the time of the accident at an airport 9 miles away was:  wind from 320 degrees at 2 knots; visibility 1/16 mile with fog; sky partially obscured; ceiling 200 feet overcast.

## Factual narrative

On September 7, 2000, at 0755 Eastern Daylight Time, a Piper PA-60-601P, N601WK, was substantially damaged during takeoff at the Northampton Airport (7B2), Northampton, Massachusetts.  The certificated commercial pilot and passenger were not injured.  Instrument meteorological conditions prevailed and an instrument flight plan was filed for the personal flight conducted under 14 CFR Part 91.

The pilot reported in a telephone interview that 7B2 consisted of a single runway oriented on a 140/320 degree heading.  The taxiway, which intersected Runway 14 at its midpoint, was oriented on a 120 degree heading.  The pilot had parked at the fixed base operator (FBO), located south of Runway 14, when he arrived at the airport the previous day.

Before departure from 7B2, the pilot instructed the passenger to "walk the length of the runway" and observe any obstructions, because the weather was "foggy, with 500-1,000 feet visibility."

According to a written statement submitted by the pilot, he said:

"I taxied to the asphalt pad by the FBO, completed my run-up and received clearance to depart from Bradley Approach.  We were relatively lightly loaded, with about 100 gallons of gas, two people and no bags, or about 700 pounds under gross and with the "balance" right in the middle of the envelope.  I expected about a 1500' takeoff roll given the weight, the 'Superstar I' engine modification, and the cool (60 degree) sea level (122') environment.  I had the approach plate (NOS) on my clipboard on my lap and reviewed the small diagram, but only 'saw' the 14-32 runway."

"I took what I thought was the runway and accelerated for takeoff.  As we hit about 80 knots (rotation was to be at 95), I realized to my dismay that we were actually on the 1000' long taxiway angling at a heading of 120 degrees into about the middle of Runway 14 and not on the runway, as I had believed."

"I immediately chopped the power and applied maximum braking.  I attempted to make the 20-degree turn to line up with the runway where the taxiway intersected, but was primarily focused on not ground looping or cartwheeling.  We missed the runway, but I got the plane turned to 140 degrees on the wet grass just at the very edge of the field, with the left wing hitting the brush along the edge.  I almost thought that we would be able to stay in the runway environment, when the left wing hit an 8-10' tree and we spun down a 10' slope, crossed a dirt road, lost our gear, and slid into a cornfield.  I was able to get the engines shut down, mags, fuel, mixtures and battery off by the time we stopped.  There was no fire despite losing the 30 gallons from the left wing and a smaller fuel leak from the right wing."

In a subsequent telephone interview, the pilot stated that he aligned his horizontal situational indicator (HSI) to a magnetic heading of 120 degrees while he was parked at the FBO.  He reported that he did not check the HSI again before takeoff.

According to the airport manager at 7B2, the taxiway which the pilot began his takeoff from was painted with a 120 degree marking and a 15 foot long yellow centerline.  The taxiway extended from a compass rose painted on the surface.  Additionally, Runway 14/32 was "clearly painted," including centerline markings, threshold markings, and runway identification numbers.  Runway 14 was 3,500 feet long and 50 feet wide, with a 300 foot displaced threshold.  The runway lights were non-standard, but "worked well."

The weather reported at 0755, at an airport 9 miles away was:  wind from 320 degrees at 2 knots; visibility 1/16 mile with fog; sky partially obscured; ceiling 200 feet overcast; temperature 43 degrees F; dew point 43 degrees F.

## Aircraft

- Registration: [N601WK](https://openairdocs.org/deregistered/N601WK-2002-10-16), registration cancelled 2002-10-16, S/N 61P07928063404, built 1980 (OpenAirDocs)
- Reported make and model: Piper PA-60-601P
- Registry model: [Piper AEROSTAR 601P](https://openairdocs.org/model/piper-aerostar-601p) (registry code 7106012) (OpenAirDocs)
- Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 61P079288063
- Airframe hours: 3595
- Engines: Lycoming IO-540 319 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Ieg Venture Management Inc
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, May 29, 2000, 53 hours before
- Departed: 7B2
- Destination: POU, POGHKEEPSIE, NY
- Flight plan: IFR
- Airport: 7B2, Northampton Airport, runway 14, 3,506 × 50 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 56; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, valid medical--no waivers/lim.; seat: left; flight hours: 4,280 total, 2,641 in this make and model, 4,200 as pilot in command, 41 in the last 90 days

## Weather

- Conditions: Instrument (IMC), Day
- Wind: 320° at 2 knots
- Visibility: 0.06 statute miles
- Lowest ceiling: 200 ft overcast
- Temperature: 43 °F, dew point 43 °F
- Altimeter: 30.00 inHg
- Observed at: CEF, 8 nm away

## 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 20000907040809A](https://openairdocs.org/incident/20000907040809A), Sep 7, 2000: Piper PA60601P, North Hampton, MA, Substantial damage. (.4) The airport consisted of a single runway oriented on a heading of 140/320 degrees. A taxiway oriented on a 120 degree heading intersected the runway at…

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.
