elihoole/asrs-aviation-reports huggingface dataset:
Date: 201602
Local time of day: 1801-2400
Location: NCT.TRACON, CA
Light: Night
Aircraft: Light Transport; Low Wing; 2 Turboprop Eng
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class E ZOA
ATC / advisory: TRACON NCT
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Clearance
Contributing factors: ATC Equipment / Nav Facility / Buildings; Procedure
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Aircraft X was inbound to SNS at 10;000 feet. He was on freq. 127.15 which usually has very good coverage. The pilot checked in at 10;000 and I descended him to 5;000 even though I thought I issued him 7;000. ZOA called me on the landline and reminded me of the MVA. I immediately instructed Aircraft X to maintain 6;400 immediately for the terrain. I issued it to him and second and third time since he wasn't responding. ZOA called again and said Aircraft X went back to their frequency because I was coming in 'broken' on 127.15.I will make sure I issue an altitude to comply with Minimum Vectoring Altitudes (MVA). Another possibility would be for aircraft below 10;000 feet inbound should be on 133.0 frequency; which has better coverage.




Synopsis: NCT Controller reported of having an aircraft inbound to a destination and descending it to an incorrect altitude. Center called and reminded the Controller of the MVA. Reporter tried calling aircraft three times to give it a correct altitude. Aircraft went back to centers frequency because reporter's frequency was coming in broken.
Date: 201911
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B777-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Airspace: Class B ZZZ
Aircraft component: Exterior Pax/Crew Door
Component problem: Malfunctioning
Reporter organization: Contracted Service
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Time Pressure
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate; Pre-flight
Result: Aircraft Aircraft Damaged; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Procedure; Company Policy
Primary problem: Procedure

Narrative: During troubleshooting of D5L passenger entry door flight lock not releasing allowing the door to be opened/closed.  The outbound Captain approached myself and the assigned Mechanic and asked several times for me (certifying engineer) to make a false logbook entry stating that the door operated normally and he would endorse the fact that he witnessed the correct operation.  Each time I refused to acknowledge his request.  The driver for his request was due to the number of passengers that would need to be offloaded due to an inoperative door.  Once it was deemed that the door would have to be deferred as 'inoperative' I was in the flight deck reviewing the (M) to be performed.At that time the Captain approached me again and said 'you know you're killing my company by doing this.  If you won't do what I had asked maybe we can find another company that will do it for us' My response was 'that's not up to me.  That's up to the company'After that there wasn't any further dialog regarding the serviceable condition of the door.




Synopsis: Technician reported outbound Captain was pressuring him to allegedly falsify a logbook entry to avoid off loading passengers due to a malfunctioning passenger door.
Date: 201902
Local time of day: 1801-2400
Location: ORD.Airport, IL
Flight conditions: IMC
Weather elements / visibility: Thunderstorm; Rain
Light: Night
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp ORD
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: Taxiing into alleyway during heavy rain/thunderstorms. [We] had just made turn to parallel terminal; when a fast-moving catering truck appeared less than 20 feet in front of the plane; traveling west on 'road' running between [two gates]. Slammed on brakes; and stopped feet from hitting him. I only saw him when my taxi light lit the truck; and then he was mostly hidden behind the windshield wiper. Several passengers made it a point to come up after we parked to tell me they saw him; and thank us for not hitting him. My impression; judging from his speed; was that he was trying to beat us; not that he didn't see a lit up 757 going no more than 10 knots. Fortunately the flight attendants were still seated; or there would have been injuries.




Synopsis: B757 Captain reported that a catering truck drove directly in front of aircraft during taxi which caused the flight crew to stop the aircraft abruptly.
Date: 201712
Local time of day: 0601-1200
Location: RSW.Airport, FL
Flight conditions: VMC
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Landing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Fatigue; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: While en route; we received an ACARS notification that the aircraft required an auto land. It was the First Officer's leg; and he planned on executing an auto land at our final destination. The weather was VMC and not a factor. We did a normal brief for the arrival and approach. We received vectors to the ILS runway 06 into RSW. After capturing the localizer and glidepath and finishing all checklists we flew the approach. On short final we both commented that the aircraft was lined up right of centerline approximately 40 feet right of centerline. The runway was 150 feet wide. We let the aircraft accomplish the auto land; which was deemed by me as unsuccessful because the aircraft remained right of centerline for the entire approach/landing/rollout. After disconnecting autopilot on rollout; we corrected back to centerline and taxied clear of runway. After logging the unsatisfactory auto land; we entered the comments into the logbook and briefed the mechanic on duty. Upon return to the airport 12 hours later; we discovered that in the airport briefing guide that auto lands to runway 06 were not authorized. I called [the company] while on ground; and explained what transpired the previous [flight] and to please notify maintenance of my erroneous write up. Comments for my performance are that I need to review airport briefing guide better and capture the error prior to commencing the approach. We were both tired after a long night of flying; and this might have been a factor in my missing the note about restricted auto lands in RSW runway 06.




Synopsis: Air carrier flight crew reported completion of an unauthorized autoland after receiving a request from the company.
Date: 201605
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was landing after ferrying the aircraft for minor maintenance. I decided to do a long soft field landing to save taxi time. The landing went well; and I held the nose off the runway for a distance then allowed it to come down. I would estimate my speed when the nose gear came down at approximately 30 knots. The nose gear began to shimmy; so I pulled the stick back to take weight off of the nose gear and the shimmying stopped; but there was not enough speed to raise the nose gear off the pavement. At this time; taxiway was coming up; and I began to apply braking at the lead-in taxiway line. At that point; the nose gear collapsed; and the aircraft skidded approximately 100 feet down the runway on its nose. I did not apply braking. Aircraft damage was confined to the propeller; cowling; nose gear and exhaust system. The nose gear showed signs of fatigue cracking.




Synopsis: PiperSport LSA pilot reported the nose gear collapsed upon landing roll out.
Date: 201203
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear Tire
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Commercial
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff; Flight Crew Returned To Gate; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Taxi out to the runway was normal. We received our takeoff clearance and applied takeoff power. Around 80 KTS felt a vibration and unusual noise. Around 110 KTS the takeoff was aborted. We reported the rejected takeoff to ATC; exited the runway and parked the airplane. [We] ran the QRH for rejected takeoff; contacted Maintenance and Operations. Airport Operations came out to the airplane and told us over the radio that both nose tires were blown. Eventually we were towed back to the gate with an electro tug.I wasn't the pilot flying; but the Captain said the aircraft's direction was difficult to control. He rejected the takeoff because the vibration and unusual noise became progressively worse. Runway centerline was maintained throughout the reject procedure.




Synopsis: A CRJ-200 flight crew rejected their takeoff when both nose gear tires failed.
Date: 201511
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Departed ramp and taxied to Runway 4. Arrived at runway 4 run-up area and performed pre-flight run-up. All indications were satisfactory and within limitations. Taxied out of run-up area to the hold short line of Runway 4. Received takeoff clearance from Runway 4 and proceeded to taxi onto runway at which point full power was added and a takeoff was initiated. Another check of the instruments was done as required and all were within limitations; RPMs were 2400; and airspeed was rising steadily. After rotation at approximately 200 feet a loud bang came from the engine compartment that sounded like the engine backfiring but normal operation continued. Upon reaching approximately 400 feet engine power loss began. Engine power dropped by about 400-500 RPMs to approximately 2000 RPMs. After the initial drop; RPMs rose by about 200 RPMs to 2200 RPMs. However; following the rise; the engine RPMs dropped in and out ranging from 200 RPM drops to 1000 RPM drops. At this point a sufficient climb was unable to be maintained due to loss of power. Tower was contacted and a request to return to the opposite direction runway (Runway 22) was made. Tower cleared all traffic from the runway and gave priority handling to us. At that point a landing was made on Runway 22. Due to excessive braking from landing on a shortened runway (only about 50% of runway was remaining at touchdown; about 2;000 feet) and a tailwind of 12 knots gusting to 19 knots the right main gear tire became worn but did not blow out. There was however a large flat spot on the tire. After making the landing; turned off the runway and returned to ramp where a secondary run-up was performed. The only noticeable problem was that when checking the right magneto a popping noise was made followed by a drop of 200-300 RPMs; but would then rise and steadily maintain an RPM setting within limitations (approximately 100 RPMs below RPM setting for run-up). Incident was reported to maintenance for further review. No damage was done to the aircraft and the instructor pilot did all flying after the initial engine power loss was observed. Student pilot and observing passenger were onboard the aircraft.




Synopsis: PA28 instructor pilot reported loss of engine power shortly after takeoff; resulting in a turn back to land at departure airport.
Date: 201502
Local time of day: 1201-1800
Location: ACY.TRACON, NJ
Aircraft: Small Aircraft
Flight plan: IFR
Flight phase: Cruise
Airspace: Class C ACY
ATC / advisory: TRACON ACY
Second aircraft: Widebody; Low Wing; 4 Turbojet Eng
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Developmental
Human factors: Confusion; Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X was IFR on V1 South at 6;000 ft.  ZDC Casino sector called with a VFR point out to descend Aircraft Y at 8;000 feet 2 miles SE of Aircraft X heading NW.  ZDC Casino sector notified me that they were aware of Aircraft X traffic and passed that traffic along to Aircraft Y.  I notified ZDC Casino that I had no other traffic that would be a factor for the Aircraft Y's descent other than Aircraft X and that their point out was approved.  ZDC Casino sector then began Aircraft Y's descent and Aircraft Y passed 2 miles in front of Aircraft X.  Then Aircraft X requested a 20 degree deviation to the right to avoid the wake turbulence.Disseminating the enroute wake turbulence separation for traffic following a heavy to all parties involved.




Synopsis: ACY Controller is working a small aircraft southbound through the airspace. ZDC controller points out a heavy military aircraft to the ACY Controller. ACY controller ensures ZDC Controller is aware of his small aircraft traffic. Point out is approved. ZDC Controller descends the heavy 2 miles in front of the small aircraft. Small aircraft pilot requests a 20 degree turn to avoid the wake turbulence.
Date: 201408
Weather elements / visibility: Thunderstorm
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure; Weather
Primary problem: Ambiguous

Narrative: Flight was planned on a route to avoid an active SIGMET area with thunderstorm tops to FL450. During taxi crew advised me that they had received a re-route. I plotted the re-route on Flight Explorer and it went through the area of weather I planned to avoid. I advised crew not to accept the reroute due to severe weather along the route. I further advised the crew to request original filed route. On the map display; I observed the flight became airborne and they had accepted the ATC assigned re-a route that would take the flight into unsafe conditions. Furthermore; the crew did not communicate their decision to disregard my safety warning. Subsequent contact efforts by the relieving Dispatcher were also ignored. Lack of communication with the Dispatcher; as well as accepting ATC re-routes without Dispatcher consent are becoming more commonplace.




Synopsis: Air Carrier Dispatcher reports a flight crew accepting an ATC reroute through weather he had flight planned to avoid and doing so against his specific advice.
Date: 202004
Local time of day: 1801-2400
Location: ZLC.ARTCC, UT
Flight conditions: VMC
Aircraft: SR20
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class E ZLC
ATC / advisory: Center ZLC
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure
Primary problem: Airspace Structure

Narrative: Aircraft X was filed ZZZ to ZZZ1 via direct ZZZ2. Aircraft X departed ZZZ; overflew ZZZ3 and was headed direct ZZZ2. Approx 5 miles south of ZZZ3 Aircraft X asked for a vector for terrain avoidance. Aircraft X was below 8;000 feet in an 110 MEA (Minimum Enroute Altitude) area and was asked if he could do the departure procedure. When he didn't respond I tried another transmitter and advised him that I was legally unable to vector him at that altitude and suggested a west heading if able. He then requested direct to a fix and was told departure procedure his discretion; cleared direct destination leaving 11;000 feet. Remind pilots to familiarize themselves with terrain and departure procedures before departing IFR at an unfamiliar airport.




Synopsis: A Center Controller reported an IFR departure did not use the published departure procedure and was below the Minimum Enroute Altitude.
Date: 201207
Local time of day: 0601-1200
Location: ZZZZ.ARTCC, FO
Flight conditions: VMC
Light: Daylight
Aircraft: B747-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While enroute at 33;000 FT; Engine EICAS indicated 3 engines [with] low oil quantity and psi. Engines were indicating 21; 14; 13; 14. Once noticed; I Sat Comm'ed the company and made them aware of the situation. Shortly thereafter Engine #4 quantity decreased to 12 and slightly less psi. Due to safety and based on the information I had; I declared an emergency and diverted the flight to [nearest suitable airport]. The flight landed safely and was terminated.




Synopsis: B747-400 Captain reported noticing low oil quantity on three of his engines. Shortly after alerting company; #4 oil quantity and pressure dropped to a level low enough that the Captain declared an emergency and diverted to the nearest suitable airport.
Date: 201503
Local time of day: 1801-2400
Location: JCT.Airport, TX
Flight conditions: Marginal
Weather elements / visibility: Cloudy; 10
Light: Dusk
Aircraft: PA-34 Seneca Undifferentiated
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Descent
Airspace: Class G JCT
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Multiengine
Human factors: Situational Awareness; Training / Qualification; Workload
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter VFR In IMC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Became Reoriented
Contributing factors: Weather; Human Factors
Primary problem: Ambiguous

Narrative: VFR flight in marginal conditions and encountered a low section of clouds that forced me to descend to approximately 600 feet and enter into the clouds momentarily.  The area was reporting 1;600 feet AGL.




Synopsis: A VFR PA-34 pilot encountered IMC and descended to 600 feet where he entered the lowest cloud momentarily.