Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

May 17, 1998 · Cessna 172A · N7222T

Van Nuys, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 17, 1998
Injury Outcomes
No injuries (1 uninjured)
Location
Van Nuys, CA
Aircraft
Cessna 172A
Tail Number
N7222T
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX98LA163

The pilot received a ground control clearance to taxi for takeoff from his transient position near the northeast side of the airport to the beginning of runway 16L. He proceeded slowly in a northerly direction and became somewhat confused regarding the route to take as he approached a barricaded area under construction. According to the pilot, he decided to use a northbound vehicle service road (instead of the taxiway) because earlier, with his flight instructor, he had used another service road near the construction area. While proceeding on the road he diverted his attention toward the active runway, and the airplane's right wing collided with a perimeter boundary fence pole. The taxiway markings in the vicinity of the accident site were subsequently inspected to ascertain their degree of conformity with Advisory Circular 150/5340-1G, Standards for Airport Markings. Deficiencies were noted in the vicinity of the barricaded detour area where the pilot reported he had previously taxied. This area was devoid of a taxiway centerline marking. Several hundred feet north of this location, at the intersection of the accident site taxiway and the vehicle service road, the minimum FAA recommended markings were present. Subsequently, the airport's management painted additional ground markings to enhance the conspicuity of the taxiway/access road intersection near the accident site.

NTSB Probable Cause

The pilot's failure to maintain obstacle clearance due to his inadequate visual lookout and selection of the wrong taxi route. Contributing factors were the pilot's diverted attention while taxiing in the vicinity of a construction area.

Full Narrative

On May 17, 1998, at 1600 hours Pacific daylight time, a Cessna 172A, N7222T, owned and operated by the pilot, collided with the airport's perimeter boundary fence while taxiing for takeoff at the Van Nuys Airport, Van Nuys, California. The airplane was substantially damaged, and the private pilot was not injured. The flight was originating at the time of the accident. Visual meteorological conditions prevailed at the time of the personal flight, and no flight plan was filed. The pilot verbally reported that he had received a ground control clearance to taxi for takeoff from his transient position near the northeast side of the airport to the beginning of runway 16L. He proceeded slowly in a northerly direction and became somewhat confused regarding the route to take approaching an area under construction. The pilot indicated that he diverted his attention toward the active runway, entered a vehicle service road in lieu of the taxiway, and while proceeding toward the runway the airplane's right wing collided with a fence pole. In the pilot's completed report he indicated that prior to the mishap he had flown with his flight instructor to finish the fourth phase of the Federal Aviation Administration's (FAA) Wings Program. During his lesson he had performed at least one takeoff and landing, and taxied on both a taxiway and a service road. The accident occurred following the dual instruction as he was attempting to return to his home base at the Whiteman Airport. In the pilot's report, he described the sequence of events leading up to the accident in the following manner: "After letting the instructor off I taxied toward the taxi-way to depart for Whiteman after contacting the tower. Upon nearing the taxi-way, I stopped to observe the situation. I noticed the taxi-way marked with black lines both to the right and to the left, the left taxi-way was also barricaded. The right side was only marked in black, therefore, I decided to use the service road to get to 16L since I had to use (the) service road to the south of this area earlier. As I started for the service road, I heard a loud noise and the aircraft veered to the right." On June 5, a representative from the Safety and Standards Branch in the FAA's Western-Pacific Regional Office (AWP-620) accompanied the Safety Board's Investigator-in-Charge and a representative from the Van Nuys Airport manager's office to perform an on-site inspection of the accident site area. The purpose of the inspection was to ascertain the degree of the municipal airport's conformity with Advisory Circular 150/5340-1G, Standards for Airport Markings. The FAA representative reported that in the vicinity of the barricaded area where the pilot reported he had previously taxied, there was no taxiway centerline marking on the Taxiway E detour from Taxiway 5D onto the airport service road and then onto Taxiway 4D. There was a continuous taxiway centerline marking on Taxiway 4D that continued northbound onto Taxiway E, which was the route that the pilot was cleared to utilize. The airport management indicated that although the airport's markings complied with the advisory circular in the accident site area, to enhance safety it would increase the conspicuity of the taxiway/access road markings near the accident intersection. Management would extend the solid taxiway edge line across the service road that the pilot erroneously used, and it would paint dashed taxiway edge lines across the tenant leasehold along the north side of taxiway 4D.

Flight

Event TypeAccident
Event Time16:00 PDT
Nearest AirportVANNUYS (0nm)
Runway16L
Runway Length4000 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172A
Tail NumberN7222T
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · O-300-C · Reciprocating · 145
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 75 · Third Class

Conditions

ConditionsVMC
LightDaylight
Wind140° @ 10 kt
Visibility15 sm
CeilingNone
Temperature / Dew Point50
Altimeter29.00 inHg
Observation Time22:57
Weather SourceWFAC

Appendix: Source Data