LAX95LA066
1994-12-30 · FORT HUACHUCA, Arizona, United States · None · 1 aircraft · Status: Completed
Airport FHU
Aircraft involved
Probable cause & findings
THE FAILURE OF THE RADAR AND TOWER CONTROLLERS TO ENSURE THAT THE PILOT WAS AWARE OF THE RUNWAY STATUS. FACTORS RELATED TO THE ACCIDENT WERE THE DOWNWIND NO-FLAP LANDING AND THE SUNGLARE.
Factual narrative
On December 30, 1994, at 0847 hours mountain standard time, the pilot of a Cessna 207, N91090, veered off runway 11 and collided with barricades and a runway construction berm at Sierra Vista Municipal Airport at Fort Huachuca, Arizona, during a Part 135 cargo flight. The aircraft was substantially damaged and the pilot was not injured. The pilot filed a company flight plan and departed Chandler, Arizona, at 0730. While en route to Fort Huachuca, the pilot requested and received an instrument flight rules clearance due to weather conditions at altitude. The investigation revealed the pilot was asked by the Libby Army Airfield Radar controller, while approaching Fort Huachuca, if she had received information Alpha, which she had not. The controller gave the winds at 210 degrees at 11 knots with the altimeter setting of 29.97 inches of mercury. The pilot confirmed later she had received this information, but the controllers neglected to mention the runway construction on runway 26 or the usable length of runway 11 being only 3,000 feet. She stated she had checked the NOTAMs the night before, but there was no mention of the barricades on runway 11 or the shortened runway length. The pilot was subsequently cleared to land on runway 11. The pilot stated she was high on the approach and kept some power on the engine due to ice on the airframe accumulated while en route. She did not use flaps and landed near the taxiway, just past the threshold. She did not notice the barricades on the runway until after she was on the ground. She applied the brakes, but realized the aircraft was not going to stop before the construction area and added power to go around. The aircraft collided with the barricades and the right main landing gear hit some concrete construction. The aircraft skidded to the right and into the dirt. She exited the aircraft and estimated the windsock was indicating a 30-knot tailwind. She also mentioned the brightness of the sun in front of her during the approach. The weather observation at the airport at 0847 was (in part): 1,200 scattered clouds; visibility 45 miles; winds from 210 degrees at 8 knots, gusting to 17 knots. Information obtained from the Federal Aviation Administration (FAA), reveals that U.S. Army personnel at Fort Huachuca posted a NOTAM regarding the runway construction on September 20, 1994, through military channels and by direct communication with the Prescott Flight Service Station (FSS). The NOTAM indicated that the southeast 2,300 feet of runway 11 was closed. Once this information is published in the NOAA Airport/Facility Directory, the NOTAM is removed from the system. Further research indicates that this information is not reflected in the Jeppesen Approach Charts, the J-AID Airport Directory, or the NOAA (U.S. Gov't.) Approach Charts. However, Jeppesen does have NOTAM information available through a subscriber service. The aircraft operator did not subscribe to this service. The operator has indicated that the Jeppesen Charts were utilized at the time, but the NOAA Airport/Facility Directory was used by only a few of the pilots. The FAA has reviewed the operations specifications for the operator and found that they were not required to have the NOAA information for airports. Since the accident, the FAA now requires the operator to use this airport directory in addition to other publications for information. A spokesman for the operator indicated that the pilot had flown into the airport on at least three occasions (October 23 & 24, 1994, and December 20, 1994) after the NOTAM was issued and should have been aware of the runway construction. EN ROUTE, THE PILOT REPLIED THAT SHE HAD NOT RECEIVED THE ATIS INFO, & WAS GIVEN ONLY THE DESTINATION WINDS OF 210 DEG AT 11 KTS AND THE ALTIMETER SETTING. AFTER BEING VECTORED & CLEARED FOR A VISUAL APPROACH TO RIGHT DOWNWIND FOR RUNWAY 26, SHE WAS CLEARED TO LAND '. . . RUNWAY ONE ONE WIND TWO FOUR ZERO AT NINER . . . .' THE PILOT ACCEPTED THE CLEARANCE TO LAND ON RUNWAY 11. THE SOUTHEAST 2300' OF THE 5365' RUNWAY WAS CLOSED. AFTER LANDING WITH NO FLAPS, THE PILOT REALIZED SHE COULD NOT STOP THE AIRPLANE BEFORE COLLIDING WITH BARRICADES & INITIATED A GO-AROUND. THE AIRCRAFT HIT THE BARRICADES & THE RIGHT MAIN GEAR COLLIDED WITH A CONCRETE BERM, COLLAPSING THE GEAR. THE WIND WAS GUSTING TO 17 KTS. THE PILOT STATED SHE HAD CHECKED THE NOTAMS THE NIGHT BEFORE & WASN'T AWARE THE RUNWAY WAS UNDER CONSTRUCTION. THIS INFO WAS PUBLISHED IN THE NOAA AIRPORT/FACILITY DIRECTORY; ONCE PUBLISHED, A NOTAM IS REMOVED FROM THE SYSTEM. IT WAS ALSO CONTAINED IN THE ATIS. THE NOAA AFD WAS NOT REQUIRED IN THE FAA-APPROVED OPERATOR SPECIFICATIONS. THE PILOT WAS USING JEPPESEN PUBLICATIONS WHICH DID NOT CONTAIN THE RUNWAY CONSTRUCTION INFORMATION, & THE OPERATOR DID NOT SUBSCRIBE TO THE JEPPESEN NOTAM SERVICE, NOR WERE THEY REQUIRED TO. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1994_LAX95LA066.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research) Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace) Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes) Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…