# Accident 19990105004159A: Piper PA31350, Anchorage, AK, January 5, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 5, 1999, 14:25 local time
- Place: Anchorage, AK
- Airport: Anchorage International
- Damage: Substantial damage
- Phase of flight: Ground Taxi, Other Airplane
- Operating rules: Air taxi and commuter (Part 135)
- Operator: IUJA
- Location: 61.1606° N, 149.9909° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=61.1606&lon=-149.9909&mi=10
- Aircraft: N6GR, registered now (https://openairdocs.org/aircraft/N6GR) (OpenAirDocs)
- Registry model: Piper PA-31-350 (registry code 7103110, https://openairdocs.org/model/piper-pa-31-350) (OpenAirDocs)
- Reported make and model: PIPER PA31350
- Reported engine: LYC TIO540J2BD
- People aboard: 6
- Fatal injuries: 0
- Pilot flight hours: 10,000 total, 1,200 in this make and model, 320 in the last 90 days
- NTSB investigation: [NTSB ANC99LA020](https://openairdocs.org/ntsb/ANC99LA020) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990105004159A

## Narrative

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

(.19) ON JANUARY 5, 1999, ABOUT 1425 ALASKA STANDARD TIME, A PIPER PA-31-350 AIRPLANE, N6GR, SUSTAINED SUBSTANTIAL DAMAGE AFTER BEING STRUCK BY A VEHICLE AT THE ANCHORAGE INTERNATIONAL AIRPORT, ANCHORAGE, ALASKA. THE AIRPLANE WAS TAXIING TO THE OPERATOR'S FACILITY AFTER LANDING. THE AIRPLANE WAS BEING OPERATED AS A VISUAL FLIGHT RULES (VFR) ON-DEMAND PASSENGER FLIGHT UNDER TITLE 14 CFR PART 135 WHEN THE ACCIDENT OCCURRED. THE AIRPLANE WAS REGISTERED TO, AND OPERATED BY JIM AIR INC., ANCHORAGE. THE CERTIFICATED AIRLINE TRANSPORT PILOT, AND THE FIVE PASSENGERS, WERE NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED. VFR COMPANY FLIGHT FOLLOWING PROCEDURES WERE IN EFFECT. THE FLIGHT ORIGINATED AT THE CHENEGA BAY AIRPORT, CHENEGA, ALASKA, ABOUT 1340. THE OPERATOR REPORTED THE AIRPLANE WAS TAXIING ON THE LAKE SHORE TAXIWAY, LOCATED ALONG THE WEST SIDE OF LAKE HOOD. A SNOW-PLOW EQUIPPED TRUCK WAS PLOWING SNOW FROM A PRIVATE AIRPLANE TIE-DOWN SPOT, LOCATED ALONG THE TAXIWAY. THE TRUCK, EQUIPPED WITH A LUMBER RACK IN THE BED OF THE TRUCK, BACKED ACROSS THE TAXIWAY. A PORTION OF THE LUMBER RACK STRUCK THE OUTBOARD END OF THE LEFT WING OF THE AIRPLANE. THE AIRPLANE RECEIVED DAMAGE TO TTHE OUTBOARD 3 FEET OF THE LEADING EDGE, INCLUDING SEVERAL WING RIBS. THE ANCHORAGE INTERNATIONAL AIRPORT PERMITS LIMITED VEHICULAR TRAFFIC ON LAKE SHORE TAXIWAY, PRIMARILY SERVICE VEHICLES AND AIRCRAFT OWNERS. IT IS NOT OPEN FOR USE BY THE GENERAL PUBLIC.  THERE ARE TWO SIGNS LOCATED ABOUT 50 FEET FROM THE POINT OF COLLISION.  ONE SIGN THAT FACES SOUTH READS, "CAUTION AIRCRAFT OPERATION AREA - YIELD TO ALL AIRCRAFT."  A SECOND SIGN THAT FACES NORTH READS, "AIRCRAFT ONLY - NO VEHICLES OR PEDESTRIANS ON TAXIWAY." (.4) THE CERTIFICATED AIRLINE TRANSPORT PILOT, WITH FIVE PASSENGERS, WAS TAXIING TO THE OPERATOR'S FACILITY AT THE CONCLUSION OF AN ON-DEMAND AIR TAXI FLIGHT.  THE TAXIWAY CONNECTS THE MAIN AIRPORT COMPLEX WITH OUTLYING OPERATOR'S FACILITIES AROUND THE PERIMETER OF A LAKE.  THE TAXIWAY HAD PRIVATE AIRPLANE TIE-DOWN LOTS LOCATED ALONG ITS LENGTH.  A SNOWPLOW EQUIPPED PICKUP TRUCK WAS REMOVING SNOW FROM A PRIVATE AIRPLANE TIE-DOWN SPOT, LOCATED ALONGSIDE THE TAXIWAY. THE TRUCK, OPERATED BY THE OWNER OF THE TIE-DOWN SPOT, WAS EQUIPPED WITH A METAL LUMBER RACK IN THE BED OF THE TRUCK. WHILE POSITIONING THE TRUCK, THE OWNER BACKED ACROSS THE TAXIWAY, INTO THE PATH OF THE ACCIDE NT AIRPLANE. A PORTION OF THE LUMBER RACK STRUCK THE OUTBOARD END OF THE LEFT WING OF THE AIRPLANE, DAMAGING 3 FEET OF THE LEADING EDGE, INCLUDING SEVERAL WING RIBS.  THE AIRPORT PERMITS LIMITED VEHICULAR TRAFFIC ON THE TAXIWAY, PRIMARILY SERVICE VEHICLES AND AIRCRAFT OWNERS.  IT IS NOT OPEN FOR USE BY THE GENERAL PUBLIC.  THERE ARE TWO SIGNS LOCATED ABOUT 50 FEET FROM THE POINT OF COLLISION.  ONE SIGN THAT FACES SOUTH READS, 'CAUTION AIRCRAFT OPERATION AREA - YIELD TO ALL AIRCRAFT.'  A SECOND SIGN THAT FACES NORTH READS, 'AIRCRAFT ONLY - NO VEHICLES OR PEDESTRIANS ON TAXIWAY.'               (-23) ON JANUARY 5, 1999, ABOUT 1425 ALASKA STANDARD TIME, A PIPER PA-31-350, N6GR, SUSTAINED DAMAGE AFTER BEING STRUCK BY A PRIVATE VEHICLE WHILE TAXIING FROM ANCHORAGE INTERNATIONAL AIRPORT TO THE OPERATOR'S HANGAR AT LAKE HOOD. THIS OCCURRED AFTER LANDING FROM A 14 CFT 135 ON DEMAND UNDER VFR CONDITIONS. THE AIRPLANE WAS REGISTERED TO AND OPERATED BY JIM AIR, INC. WHEN THE ACCIDENT OCCURRED. THE ATP CERTIFICATED PILOT AND HIS FIVE PASSENGERS RECEIVED NO INJURIES. THE FLIGHT ORIGINATED AT CHENEGA BAY, ALASKA AT ABOUT 1340.

## 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 ANC99LA020](https://openairdocs.org/ntsb/ANC99LA020), Jan 5, 1999: Piper PA-31-350 (N6GR), Anchorage, AK, substantial damage. Probable cause: The failure of the driver of a vehicle to maintain an adequate visual lookout.

## Other reports on N6GR (2)

Matched to the same aircraft by N-number and date.

- [Incident 20160315002029I](https://openairdocs.org/incident/20160315002029I), Mar 15, 2016: Piper PA-31-350 (N6GR), Milwaukee, WI, Minor damage. On March 15, 2016, at 1450 CDT a Piper navajo PA-31-350, N6GR, had an engine failure thirty minutes after takeoff from sbm, sheboygan, WI. The pilot advised…
- [Incident 20100204026949I](https://openairdocs.org/incident/20100204026949I), Feb 4, 2010: Piper PA-31-350 (N6GR), Coeur D'Alene, ID, No damage. Lost all electrical power while enroute bellingham, WA to sheridan, WY. Performed descent and emergency landing into coe. Upon landing, discovered RH…

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.
