NTSB CAROL · Event
Event IAD05LA099
Registry · N13FH
FAA Aircraft Registry record.
Make / Model
BHI H60 HELICOPTERS LLC UH-60A
Year of manufacture
1981 · 24 years old at event
Engine
GE T700-GE-700 (1561 hp)
Seats / Engines
19 seats · 2 engines
Last airworthiness date
20190131
ADS-B equipped
Yes — Mode-S A0795D
Registrant of record
BRAINERD HELICOPTERS INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's improper preflight planning, his failure to consult performance data, and his failure to obtain the proper touchdown point, which resulted in a runway overrun. Contributing factors to the accident were the excessive airspeed, overweight condition, and wet runway.
Factual narrative
HISTORY OF FLIGHT
On July 17, 2005, about 1618 eastern daylight time, a Cessna 525, N13FH, sustained substantial damage during a runway overrun while landing at Old Bridge Airport (3N6), Old Bridge, New Jersey. The certificated airline transport pilot received minor injuries, and the two passengers were not injured. Day visual meteorological conditions prevailed for the flight that departed Sussex County Airport (GED), Georgetown, Delaware. An instrument flight rules flight plan was filed for the flight conducted under 14 CFR Part 91. According to the pilot's written statement, during a visual approach for runway 24 at Old Bridge Airport, he lost sight of the runway due to clouds that had moved into the area. The clouds were associated with a thunderstorm that was about 1 to 2 miles north of the airport. The pilot notified McGuire Approach that he was executing a missed approach and requested the GPS 24 approach. He was then given a heading of 060 degrees, and told to climb to 2,000 feet msl. Approximately 3 miles from STENY intersection, which was the final approach fix, the pilot was cleared for the GPS Runway 24 approach, and proceeded directly to STENY. At approximately 1 mile from STENY, he extended the flaps to the approach position. Upon crossing STENY he then lowered the landing gear, and started his descent to the minimum descent altitude of 600 feet msl. Approximately 3 miles from the runway, the airplane's airspeed was 115 knots indicated, and he had sight of the entire airport. The visibility was better than 5 miles, and the ceiling was greater than 750 feet, with cloud to ground lightning in the area. About 2 miles from the runway he extended the flaps to the landing position, and slowed the airplane to 108 knots. He could see that the runway was wet, but was absent of standing water. He landed "on the numbers," extended the flaps to the ground position and applied full braking. After touchdown, the pilot believed that the braking action was "nil." He further stated, "I could feel no braking at all." Approximately 1/3 of the way down the runway, he decided that he did not have enough room to stop, so he applied full power and retracted the flaps to the takeoff position. The airspeed did not seem to accelerate at a normal rate, and the airplane failed to obtain flying speed. It then rolled off of the runway pavement.
PERSONNEL INFORMATION
The pilot held an airline transport pilot certificate, with multiple ratings including airplane multi-engine land, and type ratings for the Boeing 737, Cessna 500, and Cessna 525S. He reported a total flight time of 8,370 hours, with 6,293 hours in multi-engine airplanes and 795 hours in the Cessna 525. His most recent FAA first-class medical certificate was issued on December 6, 2004.
AIRCRAFT INFORMATION
The airplane was manufactured in 1997. The airplane's most recent annual inspection was completed on March 3, 2005. At the time of the inspection, the airplane had accrued 1,907.7 total hours of operation.
METEOROLOGICAL INFORMATION
The reported weather at The Monmouth Executive Airport (BLM), Farmingdale, New Jersey, 14 nautical miles southeast of the accident site, at 1615, included: winds from 160 degrees at 11 knots, gusting to 14 knots, visibility 10 miles, a broken ceiling at 1,500 feet, temperature 81 degrees Fahrenheit, dew point 75 degrees Fahrenheit, and an altimeter setting of 29.38 inches of mercury.
AIRPORT INFORMATION
Old Bridge Airport had one runway, oriented in a 06/24 configuration. The runway was asphalt, and in good condition. The runway was 3,594 feet long by 50 feet wide. Multiple obstructions existed at the approach end of runway 24, which displaced the threshold by 400 feet. A 24-foot tall tree was located 230 feet from the approach end of the runway pavement, and 20 feet left of the centerline. 19-foot high trees were located 125 feet from the approach end of the runway pavement, and 6 foot high vegetation was located 50 feet from the approach end of the runway pavement. A 26:1 approach slope to the displaced threshold was published for the runway, and the available landing length was 3,194 feet. The runway sloped downward 0.6%. A two light, 4.00 degree glide path, Precision Approach Path Indicator was installed on the right side of the runway. Airport Services were obtainable at the airport, however; no approved fuels for the Cessna 525 were available.
WRECKAGE AND IMPACT INFORMATION
The airplane came to rest on a magnetic heading of 310 degrees, approximately 400 feet beyond the departure end of runway 24, after traveling down sloping terrain where it impacted numerous objects. The upper and lower speedbrakes were in the retracted position. The wing flaps and the flap lever were in the takeoff position. Both main landing gear had collapsed, and the nose gear had separated from the airplane. Examination of the normal and emergency braking system revealed, that the brake fluid reservoir was full. When electrical power was applied to the airplane, the power brake hydraulic pump motor operated and accumulator pressure was observed to be within the normal operating range. The anti-skid switch was in the "ON" position. With the exception of a low-pressure indication in the emergency air bottle, no preimpact anomalies were noted to the brake or landing gear system.
WEIGHT AND BALANCE INFORMATION
The pilot stated that the accident flight time was approximately 35 to 40 minutes in length. The airplane had 3,250 pounds of fuel when he began to taxi, and at takeoff, was down to 3,050 pounds. He added that, this would have placed his gross weight at 10,200 to 10,300 pounds at takeoff. He also stated that the airplane's weight at landing was 9,500 pounds. A review of the fuel provider's records revealed that the aircraft was filled with 2,050 pounds of fuel, prior to the accident flight. According to the fueler, the fuel order he had received from the pilot was to "top it off."
TESTS AND RESEARCH
According to the FAA approved flight manual, the fuel system on the airplane holds approximately 3,220 pounds of usable fuel when filled to the bottom of the filler standpipe. It is also possible to exceed that amount by 220 more pounds of fuel, if the wing is filled to the top of the standpipe.
ADDITIONAL INFORMATION
Enhanced Ground Proximity Warning System The airplane was equipped with an Enhanced Ground Proximity Warning System (EGPWS). Information obtained from the EGPWS revealed that approximately 0.1 nautical miles prior to the runway threshold, the airplane's ground speed was 133 knots, and the descent rate was 1,522 feet per minute. At the same time, the unit announced an aural "sink rate" warning. The data also indicated that the airplane contacted the runway approximately 0.2 nautical miles (1,215 feet) beyond the runway threshold. Review of Available Performance Information A review of Section IV and VII of the FAA approved flight manual revealed that landing performance information was available to the pilot. Standard performance conditions were based on a landing preceded by a steady 3 degree angle approach, down to the 50 foot height point with airspeed at 1.3 times the stalling speed or the minimum steady flight speed in the landing configuration. Variable factors for wind, wet runway conditions and runway gradient was also available. According to published performance information, at 9,500 pounds, airspeed at the 50-foot height point should be 107 knots. In a no wind condition, with a dry and level runway, the airplane required a landing distance of approximately 2,770 feet. The Advisory Information Section VII corrections for a wet runway increased that distance to approximately 3,550 feet. During an interview conducted by the Safety Board on July 22, 2005 the pilot stated that he was "not sure if I looked at the wet runway stuff." On approach the EGPWS "blipped once" but he believed that nothing was out of the ordinary. He also believed that he touched down on all "three gears" just beyond the "numbers," which is what he was aiming for.
WRECKAGE RELEASE
The wreckage was released to a representative of the owner's insurance company on August 17, 2005. The airplane departed with a full load of fuel, flew approximately 35 minutes, and upon touchdown, weighed approximately 9,500 pounds. According to data recovered from the Enhanced Ground Proximity Warning System, the approach became unstabilized 0.1 miles from the runway threshold, triggering an aural sink rate warning. The airplane touched down fast on the first 1/3 of the runway. The pilot realized the airplane would not stop in the remaining distance, so he aborted the landing; however, before becoming airborne, the airplane overran the runway, struck multiple objects, and was substantially damaged. According to performance information, at 9,500 pounds, on a wet runway, 3,550 feet was required, 306 feet greater than available. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_IAD05LA099.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, thunderstorm). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NTSB Safety Studies 2019 · Safety study
Bell 525 Relentless In-Flight Breakup
Investigation report and safety study on the 6 July 2016 in-flight breakup of a Bell 525 Relentless helicopter prototype during a developmental flight test near Italy, Texas.
- NTSB Aircraft Accident Reports 2019 · Accident report
In-Flight Breakup of Bell 525 Relentless Helicopter
Bell 525 prototype helicopter in-flight breakup near Italy, TX, July 6, 2016 — 2 fatalities. Investigation of the developmental-flight-test in-flight breakup of a Bell 525 Relentless prototype.
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
The Impact of Thunderstorms on Take-off Data in South Africa
Aviation and meteorology are entwined disciplines, as aviation occurs in the atmosphere. Prevailing weather conditions at take-off are of utmost importance to aviation.
- arXiv 2023 · arXiv preprint
Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint
Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
Browse the full corpus — academia portal ↗