NTSB CAROL · Event
Event IAD05CA098
Aircraft involved
Probable cause & findings
The pilot's misjudgment of distance/altitude, and his failure to maintain obstacle clearance.
Factual narrative
On July 15, 2005, at 0530 eastern daylight time, a Grumman G-164A, N48408, was substantially damaged when it struck wires, then collided with terrain while on final approach to the Southern Cross Airport (C01), Williamstown, New Jersey. The certificated commercial pilot was not injured. Visual meteorological conditions prevailed for the local positioning flight that departed Southern Cross Airport, about 0525. No flight plan was filed for the flight conducted under 14 CFR Part 91. The pilot provided both a written statement and a telephone interview. He explained that the purpose of the flight was to check the local weather where he was contracted to spray crops. After takeoff, he determined that the weather was worse than reported, and he returned to the airport. The pilot stated that while on final approach, the airplane began to "settle," and that he was "slow" in his response. The pilot increased engine power, but the airplane struck wires and terrain prior to the approach end of runway 09. When asked about the performance and handling of the airplane, the pilot responded, "The airplane was fine. The engine was running perfectly. I'm not blaming anyone but me." In a subsequent conversation, the pilot added that he managed the airport, knew the wires were there, and that they were marked. The pilot held a commercial pilot certificate with ratings for airplane multi-engine land, single engine land, single engine sea, and instrument airplane. He also held a flight instructor certificate with a rating for airplane single engine land. The pilot was issued a Federal Aviation Administration (FAA) second-class medical certificate on March 4, 2005. He reported 17,444 hours of flight experience, approximately 2,500 hours of which were in make and model. The weather reported at Philadelphia International Airport (PHL), 16 nautical miles northwest of the airport included wind from 140 degrees at 3 knots. There were scattered clouds at 500 feet, and an overcast layer at 1,000 feet. The visibility was 5 miles in fog. After takeoff, the pilot determined that the weather was worse than reported, and he returned to the departure airport. While on final approach, the airplane began to "settle," and the pilot was "slow" in his response. He added power, but the airplane struck wires and terrain prior to the approach end the runway. When asked about the performance and handling of the airplane, the pilot responded, "The airplane was fine. The engine was running perfectly. I'm not blaming anyone but me." In a subsequent conversation, the pilot added that he managed the airport, knew the wires were there, and that they were marked. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_IAD05CA098.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.