elihoole/asrs-aviation-reports huggingface dataset:
Date: 201307
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Aircraft component: Rudder Control System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Attendant
When detected: In-flight
Result: General Maintenance Action; General Release Refused / Aircraft Not Accepted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During a thru flight stop; a Flight Attendant told me she heard a loud noise in the tail section that sounded like a thumping that was continuous. The aircraft had had a lightning strike a few days prior to our flight. Maintenance had also done some flight control repairs prior to our flight. I decided to call Dispatch and through them Maintenance Control. I had the First Officer move the rudder and I listened to see if I could hear the noise; which I did. Contract Maintenance was called and the plane was taken out of service.


Second narrative: After landing and parking aircraft during thru flight it was brought to the attention of the flight crew by a Flight Attendant of noise coming from rear of aircraft. Upon further inspection by Crew and Contract Maintenance; noise and vibration was a result of the rudder control as it was moved on the ground.


Synopsis: During an enroute stop a Flight Attendant reported a continuous 'thumping' noise in the aft body. The flight crew determined it to be related to rudder operation and; having occurred subsequent to recent flight control maintenance at the previous stop; it was deemed unfit for service.
Date: 201605
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Confusion
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Flight Deck / Cabin / Aircraft Event Other / Unknown; Ground Event / Encounter Vehicle
Detector: Person Flight Attendant
When detected: Taxi
Result: Aircraft Aircraft Damaged; Flight Crew Became Reoriented; General Maintenance Action
Contributing factors: Human Factors; Airport; Procedure
Primary problem: Human Factors

Narrative: Taxiing North on K; assigned spot X for [our] gate. Made left turn. Catering truck was parked behind double yellow line by the island; off the right wing. I was on my line for [our spot] taxing west prior to turning north for gate to clear [at spot Y]. Got a call from back of aircraft. First Officer answered phone and told me to stop. I was informed at that time; the right wing had struck the catering truck. Contacted ramp; and informed them of the damage. Contacted the Union; and was informed to pull CVR; contact maintenance; Chief Pilot on Duty and make Log book entry.Better markings and lines that would designate inadequate clearance for aircraft and obstacles.


Second narrative: One of the Flight Attendants called and told us to stop the aircraft because we had clipped a truck. We notified ramp and then; continued to taxi to the gate. After completing the parking checklist; we made the appropriate AML entry.


Synopsis: Air carrier flight crew reported their right wing tip impacted a catering truck parked behind the double yellow. The Captain stopped and assessed the situation; then continued to the gate for maintenance.
Date: 202107
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Weather elements / visibility: Haze / Smoke; 9
Aircraft: Robinson R22
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Second aircraft: Cessna Single Piston Undifferentiated or Other Model
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Time Pressure
Anomaly: Conflict NMAC; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: When flying left traffic patterns for taxiway parallel [Runway] XX with a student pilot; a plane taking off a parallel Runway XX turned an early left crosswind at 300 AGL after we had turned our crosswind at 300 AGL in a helicopter. Upon hearing the radio call; I glanced over my left shoulder knowing their relative location upon climbout. I found them almost directly above and to my left making a left hand turn that was leading into our course. I immediately descended to approximately 150 AGL to build separation from the craft and turned to the right to avoid a collision course. I called out upon the radio to connect with the the other aircraft and no response was received from the other pilot; who I came to find out was a solo student. The plane was flying extremely tight patterns cutting off the flow of helicopter traffic that is typically flying on the adjacent taxiway. With two flight schools based at ZZZ; there is a lot of student traffic. Procedures and policies have been put in place; but lack of situational awareness from students causes a lot of mishaps such as the events of today.




Synopsis: R-22 Instructor reported an NMAC event during landing pattern training. R-22 executed an evasive maneuver to prevent  a collision with a solo student on parallel runway.
Date: 201902
Local time of day: 1801-2400
Location: JFK.Airport, NY
Flight conditions: VMC
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower JFK
Second aircraft: B747 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Gate; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: After being cleared to line up and wait by ATC behind a departing 747; we started slowly moving toward the runway after the 747 was already on the roll. As the departing traffic was a considerable ways into his take off; we had just passed the hold short line. At that point; we felt the right side of the aircraft begin to lift and the aircraft began to roll to the left. It is difficult to say how much the airplane rolled left but was very defined. After about 2 seconds; the airplane returned to its normal level position on the ground. At this point; we decided not to attempt take off and a taxi off the runway. We requested this with ATC and advised them of our wake encounter. After taxiing off the runway; we decided the best course of action was to return to the gate and have Maintenance inspect the airplane; even though we felt there was no wingtip contact or any other damage. While the Captain was coordinating with ground; I was talking to operations and Maintenance advising them of our situation and that we requested a gate and Maintenance to come look at the airplane. Upon returning to the gate; the aircraft was inspected and cleared. We departed the gate again and the flight went as planned. The wake  of the 747 and high; shifting winds; (gusting 35kts plus) I believe caused the encounter. We were just crossing the hold short line not directly behind the departing aircraft when we started to roll and had given what seemed like adequate time and distance for the wake to dissipate and become a non-issue. Be more cautious when moving the aircraft in high wind and heavy aircraft departures.




Synopsis: CRJ-200 First Officer reported that while lining up; the aircraft rolled due to jet blast from a departing B747.
Date: 201702
Local time of day: 1801-2400
Location: ZDC.ARTCC, VA
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were given a clearance from to descend to FL320 and then to descend via the TRUPS3 arrival. I was descending in FPA mode and before we leveled off at FL320 I set the lowest altitude on the arrival in the alt select window. The plane descended below FL320; which was ok; but I didn't want to descend that early so I climbed about 600' back up to FL320. I then selected VNAV and reselected the lowest altitude on the arrival. As we were climbing; the controller asked us what we were doing. We told him that we were climbing back up to FL320 before descending via the arrival. The controller then told us that once we go below that altitude that we were not allowed to go back up to it. I did not know this as I thought we were cleared from FL320 and below. There were no traffic conflicts and the rest of the flight continued without incident.I did not realize at the time that what I was doing was not allowed as the controller said. I know now not to do this again. Looking back; I should have asked the controller if I could go back up to FL320 or level off at an altitude below; before intercepting the glidepath of the arrival.


Second narrative: [Report narrative contained no additional information.]


Synopsis: EMB-175 flight crew was cleared to descend to FL320 then via the TRUPS3 arrival. The Captain descended through FL320; which was acceptable; but had intended to stop at FL320 and climbed back up. This resulted in an admonishment from ATC.
Date: 201506
Local time of day: 1201-1800
Location: ZAU.ARTCC, IL
Light: Daylight
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZAU
ATC / advisory: Center ZAU
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Time Pressure; Distraction; Communication Breakdown; Workload
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Clearance
Contributing factors: Procedure; Airspace Structure; Human Factors
Primary problem: Procedure

Narrative: There is a procedure in place for GYY arrivals with a portion of it having too steep of a descent for aircraft to comply. The route is supposed to be POOGY COOKS with the RBS 45 sector crossing 10 NM S of POOGY at FL240 then COOKS at 17;000 FT. My airspace lies between FL230 and COOKS at 17;000 FT; so I am dependent on the sector before [mine] to meet their restriction and transfer communication in time to issue the COOKS at 17;000 FT crossing. There is approximately 25 miles for aircraft to descend 7;000 FT. A factor that makes this more challenging is aircraft usually have a tailwind on the heading to COOKS. Today; Aircraft X was cleared direct COOKS by the previous sector; did not APREQ [Approval Request] direct COOKS and was too high to make the crossing at COOKS. When I received communications with Aircraft X; had less than 10 NM to make the crossing. I was forced coordinate Aircraft X descending with the next sector beginning just after COOKS. Coincidentally; upon communications transfer to Sector NEWTT/EON 43/44; the aircraft did not respond and was NORDO[No Radio]. Communication with Aircraft X was reestablished well inside NEWTT/EON 43/44 airspace without incident.The RBS sector failed to coordinate the aircraft not meeting the SOP. The SOP route and altitude restriction is not feasible for aircraft to fly when the SOP restrictions are made. The procedure should be designed to go from RBS 45 to NEWTT/EON 43/44. A route of RBS LUCIT would move the GYY aircraft further South; which would aid 43/44 in missing their South departure traffic. It would be a more direct route and it would stay in one area rather than go from the South Area; the Southwest Area; then back to the South Area. The descent profile should be shallowed out with RBS 45 getting aircraft to FL240 earlier to account for any traffic situations between FL240 and 17;000 FT.




Synopsis: ZAU Controller reports of an aircraft coming in high from a previous sector during handoff which resulted in a missed crossing restriction and an increase in controller workload. The enroute Controller makes recommendations on how to remedy the situation.
Date: 201812
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climb out the flight attendants smelled smoke in the back of the aircraft. We [notified ATC] returned for landing.


Second narrative: [Report narrative contains no additional information.]


Synopsis: B757 flight crew reported a Flight Attendant smelled smoke in the back of the aircraft.
Date: 202007
Local time of day: 1801-2400
Flight conditions: VMC
Weather elements / visibility: 10
Light: Dusk
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Observer
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: My student was on his last landing of solo lesson; flying Aircraft X and so far; everything was going well. On his last landing everything looked good down to the touchdown. But it looks like he got on the brakes as the airplane touched down. The plane started to swerve side to side; at this point I got on the radio and told him to let off on the brakes. I could hear the tires skidding and maybe the wheels locking up. I think the student over-control and aggravated the situation; the plane swerved hard and went off the runway to the left. The airplane entered the grass just before runway XX-YY. The left wing looked like it contacted the ground and the one thousand feet remaining sign. The airplane came to rest on the side of runway XX-YY. The left-wing tip received substantial damage from the impact with the sign and possibly the ground. The student said he was not injured. During the review flight before the solo everything went well the student had a tendency of being left of centerline. But we work on that and he was maintaining centerline pretty well. We also talked about being gentle on the brakes and not trying to force making the taxi way.




Synopsis: Instructor reported observing student have a runway excursion upon landing.
Date: 201807
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Robinson Helicopter; Undifferentiated or Other Model
Operating under: Part 91
Mission: Training
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Electrical Power
Component problem: Failed
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Was flying with a student headed east from [origin] airport over terrain and encountered an electrical failure with the helicopter- was able to take control of the throttle and fly it safely to the ground. Called friends for help and trailered the aircraft to [our destination].




Synopsis: R44 Pilot reported that the aircraft encountered an electrical failure in flight.
Date: 201810
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ground ZZZ; Ramp ZZZ
Second aircraft: B737-700
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Ground Event / Encounter Aircraft
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: After landing on in ZZZ; we were cleared to proceed to the gate. Upon arriving at [the] gate in ZZZ; a baggage cart was parked inside/on the Safety line. We requested Ground Crew to remove cart from Safety zone. While awaiting Ground Crew to complete removal of ground cart; aircraft was struck on the right side of the horizontal stabilizer by an aircraft attempting to maneuver behind us. Communication was established with the aircraft that struck us and confirmed the damage. Elected to shut down the aircraft in place and be towed into gate.


Second narrative: During taxi into the Gate we noticed that there was a baggage cart slightly over the right side Safety line. Since we had split-scimitar winglets; the Captain decided to hold on the gate centerline outside of the Safety Zone until Ground Ops moved the cart. While the cart was being moved we heard and felt a shudder to the aircraft. We could see a Company aircraft behind us so we asked Ground if they could see our aircraft to determine if we had contacted each other. The Crew from the other aircraft replied on the radio that they had clipped us.Our next actions were to determine the extent of the damage over the radio; remind the Passengers to remain seated and to alert the F/As (Flight Attendants) of our situation. The F/As said they felt the strike; but there were no abnormal situations in the cabin. After talking to the Crew behind us; the F/As and to Ground Control; we didn't feel there was an emergency situation; so we didn't call for emergency support. Although; since the full damage to our aircraft wasn't known; the Captain elected to shut down the engines and have the aircraft towed in to the gate. After shutting down the engines; we ran the Parking Checklist and called Ops to coordinate a tug. The aircraft behind us had clipped our right horizontal stabilizer with their left winglet and tore a piece of it off.After parking; the Captain called the Chief Pilot on Call to alert them and Dispatch of the situation. The Captain wrote up the defect and briefly talked with Maintenance; who took control of the aircraft after de-boarding. We then contacted scheduling to let them know we were told to stay with the aircraft.


Synopsis: Flight crews of two B737s reported a ground collision when the winglet of the taxiing aircraft struck the tail of the parked aircraft.
Date: 201503
Local time of day: 1201-1800
Location: MGM.Airport, AL
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Flight plan: IFR
Flight phase: Landing
Airspace: Class D MGM
ATC / advisory: TRACON MGM; Tower MGM
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object; Inflight Event / Encounter Object
Detector: Person Flight Crew
Contributing factors: ATC Equipment / Nav Facility / Buildings; Equipment / Tooling; Human Factors; Procedure
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Aircraft X was inbound for runway 10 on the GPS approach.  The wind had been less than 5 knots; but then it started gusting to 25009G17.  I advised the aircraft that tower would have to change runways; but that there was a raised cable to runway 10 that would need to be taken down.  I also advised the aircraft that I could either take the aircraft out for holding until this was accomplished; or that he could continue inbound and possibly circle once the runway change was complete.  I then told him that if the cable could not be taken down in time he could do a missed approach back for resequencing; or that he could land over the raised cable.  The pilot advised he could do either one.  Then I cleared the aircraft for the approach and shipped him to the tower.  Tower cleared him to circle to the other runway once it was active; but did not mention the raised cable again.  The pilot landed and crossed over the cable which he claims cracked the wheel covers on the aircraft.The aircraft could not be given the option to land over the raised cable; but instead resequenced to hold until the cable and runway change was entirely completed.




Synopsis: A Montgomery (MGM) Approach Controller describes advising an aircraft that the runway direction is changing; and an arresting cable needs to be lowered. The pilot elects to land over the cable after being given a few options by the Controller. The aircraft is switched to Tower and lands impacting the cable and damaging the aircraft.