# Accident 19990813012039A: Piper PA18125, Anchorage, AK, August 13, 1999 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: August 13, 1999, 17:05 local time - Place: Anchorage, AK - Airport: Anchorage International - Damage: Substantial damage - Phase of flight: Takeoff Ground Roll - Operating rules: General operating rules (Part 91) - Location: 61.2195° N, 149.8495° W: From the FAA, an estimate near the named town, within about 3 miles - Nearby events: https://openairdocs.org/map.md?lat=61.2195&lon=-149.8495&mi=10 - Aircraft: N1386A, registered now (https://openairdocs.org/aircraft/N1386A) (OpenAirDocs) - Registry model: Piper PA-18-125 (registry code 7101812, https://openairdocs.org/model/piper-pa-18-125) (OpenAirDocs) - Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs) - Reported make and model: PIPER PA18125 - Reported engine: LYC O320* - People aboard: 2 - Fatal injuries: 0 - Pilot flight hours: 625 total, 15 in the last 90 days - NTSB investigation: [NTSB ANC99LA113](https://openairdocs.org/ntsb/ANC99LA113) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/19990813012039A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (TTY) ACFT GROUND LOOPED ON TAKEOFF. (.19) ON AUGUST 13, 1999, ABOUT 1705 ALASKA DAYLIGHT TIME, A TUNDRA TIRE EQUIPPED PIPER PA-18 AIRPLANE, N1386A, SUSTAINED SUBSTANTIAL DAMAGE DURING TAKEOFF FROM THE ANCHORAGE INTERNATIONAL AIRPORT, ANCHORAGE, ALASKA. THE AIRPLANE WAS BEING OPERATED AS A VISUAL FLIGHT RULES (VFR) CROSS-COUNTRY PERSONAL FLIGHT WHEN THE ACCIDENT OCCURRED. THE AIRPLANE WAS OPERATED BY THE PILOT. THE PRIVATE CERTIFICATED PILOT, AND THE SOLE PASSENGER, WERE NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED. A VFR FLIGHT PLAN WAS FILED FOR IGIUGIG, ALASKA, BUT NOT ACTIVATED. DURING A TELEPHONE CONVERSATION WITH THE NATIONAL TRANSPORTATION SAFETY BOARD (NTSB) INVESTIGATOR-IN-CHARGE (IIC), ON AUGUST 16, 1999, THE PILOT REPORTED HE WAS BEGINNING A TAKEOFF ROLL ON RUNWAY 32. HE SAID A LEFT CROSSWIND CONDITION EXISTED AT THE TIME. HE UTILIZED 2 NOTCHES OF FLAPS FOR THE TAKEOFF. DURING THE TAKEOFF ROLL, THE LEFT WING BEGAN TO RISE, AND THE AIRPLANE VEERED TO THE RIGHT. THE AIRPLANE GROUND LOOPED TO THE RIGHT, AND THE LEFT WING STRUCK THE RUNWAY. THE PILOT SAID THE LEFT WING RECEIVED SPAR DAMAGE. AT 1718, AN AVIATION ROUTINE WEATHER REPORT (METAR), ANCHORAGE INTERNATIONAL AIRPORT, WAS REPORTING IN PART: WIND, 240 DEGREES (TRUE) AT 7 KNOTS; VISIBILITY, 10 STATUTE MILES; CLOUDS AND SKY CONDITION, FEW AT 2,000 FEET; TEMPERATURE, 64 DEGREES F; DEW POINT, 51 DEGREES F; ALTIMETER, 29.84 INHG. (-23) THE PILOT ATTEMPTED TO TAKEOFF FROM RUNWAY 32 AT ANCHORAGE INTERNATIONAL AIRPORT. HE STATED THAT HE HAD A 6-8 KNOT LEFT CROSSWIND. THE LEFT WING LIFTED UP, DRAGGING THE RIGHT WING ON THE ASPHALT. THE AIRCRAFT THEN GROUNDLOOPED AND CAME TO A STOP OFF THE RIGHT SIDE OF RUNWAY 32. (.4) THE PRIVATE CERTIFICATED PILOT WAS BEGINNING A CROSS-COUNTRY FLIGHT ON RUNWAY 32. THE PILOT SAID A LEFT CROSSWIND CONDITION EXISTED, AND DURING THE TAKEOFF ROLL, HE UTILIZED 2 NOTCHES OF FLAPS. DURING THE TAKEOFF, THE LEFT WING BEGAN TO RISE, AND THE AIRPLANE VEERED TO THE RIGHT. THE AIRPLANE GROUND LOOPED TO THE RIGHT, AND THE LEFT WING STRUCK THE RUNWAY, RECEIVING SPAR DAMAGE. THE WIND CONDITION AT THE AIRPORT WAS 215 DEGREES (MAGNETIC) AT 7 KNOTS. ## 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 ANC99LA113](https://openairdocs.org/ntsb/ANC99LA113), Aug 14, 1999: Piper PA-18 (N1386A), Anchorage, AK, substantial damage. Probable cause: The pilot's inadequate compensation for wind conditions during takeoff. A factor was a crosswind, and an inadvertent ground loop. ## Other reports on N1386A (5) Matched to the same aircraft by N-number and date. - [Accident 20171129022329A](https://openairdocs.org/incident/20171129022329A), Nov 29, 2017: Piper PA-18-125 (N1386A), Tatitna, AK, Substantial damage. The pilot was doing a test landing to determine the depth and drag of the snow. Upon the first pass and initial touchdown there was excessive and unforeseen… - [Incident 20060523008229I](https://openairdocs.org/incident/20060523008229I), May 23, 2006: Piper PA18125 (N1386A), Chigagoft Bay, AK, Minor damage. (-23) Pilot and 1 pax took off in 30KT gusty right hand crosswind on a sloped beach. After take off pilot encountered wind gust that drifted airplane over the… - [Accident 20030923036399A](https://openairdocs.org/incident/20030923036399A), Sep 23, 2003: Piper PA18125 (N1386A), Tanana, AK, Substantial damage. (-23) Pilot stated that 20 knot winds and low level turbulence at tree-top level, light winds with occasional gusts at the surface caused the left wing to… - [Accident 19970626016009A](https://openairdocs.org/incident/19970626016009A), Jun 26, 1997: Piper PA18125 (N1386A), Birchwood, AK, Substantial damage. Lost power on climbout. Turned back landed in trees. Fuel selector o ring split. No detenies. Water in magas fuel. - [Incident 19790803029919I](https://openairdocs.org/incident/19790803029919I), Aug 3, 1979: Piper PA18125 (N1386A), Chugiak, AK, Minor damage. Pilot lost directional control after touchdown. 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.