elihoole/asrs-aviation-reports huggingface dataset:
Date: 201405
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 15
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class E ZZZ
ATC / advisory: UNICOM ZZZ
Reporter organization: Personal
Reporter function: Captain; Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: After entering the traffic pattern using a 45 degree entry; I was established (and reported such on the Unicom frequency) on the left downwind of the landing traffic pattern. Other aircraft entered the traffic pattern on a crosswind leg at midfield from which he was going to enter the same left downwind leg that I was flying. At same altitude (traffic pattern altitude) he passed in front of me by no more than 150 feet while beginning his left turn to the left downwind leg. I commented that he had just cut me off and we had come to within 150 feet of each other. He responded that he never saw me. While it was day VFR; I had my aircraft illuminated with landing lights; red tail strobe and wingtip strobes. We had a very heated exchange on the ground. It was clear that he had no clue who has the right of way in a traffic pattern; or that he would ever admit he was wrong. (As a side note; he arrogantly stated: 'I'm a retired airline Captain with 25;000 hrs; what are your qualifications?'  When I replied that I was also a retired airline Captain with the same amount of flying time; he told me to 'get the [expletive] off 'my' ramp. I told him the ramp was [not owned by him] and left. A loose cannon for sure.




Synopsis: This ATP pilot; flying a small single engine G/A airplane in the traffic pattern at an uncontrolled airport and conforming to expected radio protocol; reports a near miss with another aircraft apparently not communicating.
Date: 201903
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Reporter organization: Contracted Service
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Confusion; Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
Result: General None Reported / Taken
Contributing factors: Procedure; Human Factors; Company Policy; Incorrect / Not Installed / Unavailable Part
Primary problem: Human Factors

Narrative: When I was assigned to the slide shop I installed O-rings from the Goodrich parts cabinet that have been determined to have the wrong effectivity. I also installed yellow electrical tape supplied by company on Air Cruiser Slides as instructed. This tape was also found to have the incorrect effectivity.Buyers or whoever purchases parts for components should check effectivity for components they are to be used on; and alert Supervisors and mechanics when manufacturer makes changes or upgrades to parts.




Synopsis: B737 Maintenance Technician reported that incorrect parts were installed on passenger emergency exit slide packs.
Date: 201202
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Conflict NMAC
Detector: Automation Aircraft TA; Automation Aircraft RA
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: [We were] descending into our destination from 12;000 to 11;000 FT. At about 11;500 FT; got a TA followed by an RA at 11;300 FT for an aircraft below us at -300 FT on TCAS. Aircraft was supposed to be VFR at 10;500 FT. [It] passed under us at about 200 FT. Followed CLIMB RA to 11;500 FT. Advised ATC and returned to 11;000 FT. Cause [was] Approach descending us into known traffic with less than 1;000 FT separation. ATC should not descend aircraft into known VFR aircraft with less than 1;000 FT separation within 3 miles of our position.




Synopsis: Air Carrier Captain described a TCAS TA/RA event when they descended to an altitude separated by 500 FT from VFR traffic. The reporter suggested that ATC always provide IFR separation; i.e 1;000 FT and 3 miles.
Date: 202102
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: 40
Light: Night
Aircraft: Citation I/SP (C501)
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Approach
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Personal
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown; Human-Machine Interface; Situational Awareness
Anomaly: Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were transitioning in VFR conditions on the ZZZZZ3 arrival to the GPS approach to XXR. We loaded the approach into the FMS and set bottom attitude for the approach. I was in right seat flying and CA was in the left who is a CE510s rated pilot also. I was off auto pilot and hand flying with a different flight director display than normally used. The issue was when engaged the appr mode on flight director while still in Vnav instead of waiting until the GPS switched to LPV mode just outside of the final approach fix. The controller advised us that we had descended below the minimum vectoring altitude for that segment of the approach. The clear message here was that better crew coordination was needed.




Synopsis: C501 pilot reported that while handflying an approach ATC advised them that they had descended below the MVA for the segment before the FAF.
Date: 202110
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ground ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew; Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Electrical smell aircraft right- around rows 8;9;10. Before boarding flight attendants heard continuous bells. FA4 mentioned to FA1 two call bells were flashing around rows 8;9;10. FA2 also mentioned to FA1 that there was an occasional crackling; sizzling noise. FA1 asked the First Officer who was standing in forward entry area to come to rows 8;9;10 to listen to noise. FA1 mentioned to First Officer that she could smell electrical smell/odor. No smoke just an electric smell/odor. FA1 noticed caution light on CIDS panel was illuminated. First Officer went to inform Captain. Captain told FA1 that they were going to shut down power to aircraft. FA1 informed FA2 and FA4 that power was going to be shut off. After power was shut off smell/odor was no longer noticed. Mechanics came on board. Flight service manager came to aircraft to check on flight attendants as well as get information on smell/odor. Pilots informed flight attendants that we would be changing aircraft.




Synopsis: A319 Flight Attendant reported a fume event during preflight. Maintenance troubleshot the issue and a different aircraft was assigned.
Date: 201208
Local time of day: 0601-1200
Location: ZOA.ARTCC, CA
Flight conditions: Mixed
Weather elements / visibility: Rain; Turbulence; 20
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZOA
ATC / advisory: Center ZOA
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Weather
Primary problem: Weather

Narrative: En route southbound on V113; Nexrad weather showed areas of medium precipitation. I was in visual conditions and could see the clouds were just above my cruising altitude. I requested a 20 degree deviation from ATC which was approved. Shortly after turning to deviate away from the medium precipitation; I encountered a downdraft that caused me to lose 700 FT from my assigned altitude of 9;000 FT to approximately 8;300 FT. ATC asked about my altitude and I responded that I was in a downdraft and requested lower. ATC cleared me to descend and maintain 7;000 FT.




Synopsis: C172 pilot encounters a strong downdraft flying below storm clouds at 9;000 FT and looses 700 FT inadvertently. ATC questions the descent then assigns 7;000 FT as requested.
Date: 201401
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
Aircraft: Merlin Undifferentiated or Other Model
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Aerofoil Ice System
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain; Single Pilot
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climb 'Right Wing Overheat' annunciator light came on steady. I proceeded using the emergency checklist to resolve the issue. I alerted Center of the annunciator light and that I needed to deviate. Center offered a return to the departure Airport and I accepted. The annunciator light did not extinguish during the return to the airport until the taxi off of the runway.




Synopsis: Merlin pilot experiences a 'Right Wing Overheat' annunciator light during climb in VMC. The appropriate emergency checklist is consulted and the flight returns to the departure airport. The annunciator does not extinguish until after landing.
Date: 201912
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: EMB ERJ 140 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: In a discussion after takeoff; the First Officer and I are unsure as to whether the runway lights were on for our takeoff. I distinctly remember relying on much of the airport lighting taxiing out from the terminal; including taxiway lighting and the PAPI's for our runway being visible. We simply can't remember if the runway edge lights were illuminated. We had not done many 'kickoff' flights recently and this airport was uncontrolled at this time in the morning.It will be good practice to reactivate the lights again before taking the runway to ensure they remain illuminated for the takeoff roll.




Synopsis: EMB-140 Captain reported the flight possibly took off from a non-towered airport without activating all the runway lighting.
Date: 201910
Local time of day: 1201-1800
Location: ISM.Airport, FL
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Initial Approach
Airspace: Class D ISM
ATC / advisory: Tower ISM
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Flight Instructor
Human factors: Distraction; Situational Awareness
Anomaly: Conflict NMAC; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was on the VOR/DME A approach. ATC instructed us to maintain 1;500 feet and to go all the way to the missed approach point before going missed due to other traffic that was in the pattern. This seemed fairly routine to me. I carefully explained to my student what ATC meant and he understood what was going on. As we continued I kept my scan going outside to ensure we would not collide with anything. Directly over the airfield just before we reached the Missed Approach Point I glanced left and saw a drone of some type at our altitude and with 500 feet of us. After the initial shock of seeing a drone that high I realized that it would not hit us. I notified ATC immediately of the drone that was over the airfield and the Controller seemed shocked to hear that report from me. After that he handed me back off to approach.




Synopsis: A pilot reported an NMAC with a Drone while on approach to ISM airport.
Date: 201708
Local time of day: 0601-1200
Location: JNX.Airport, NC
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
ATC / advisory: CTAF JNX
Reporter organization: Corporate
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Distraction
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While taxiing to runway 3 at JNX; I became distracted by an aircraft that seemed to be having difficulty landing. I did not realize I had reached the end of the taxiway until I was very near the turn towards the threshold of runway 3. I was unable to stop and ran off the taxiway. Right rudder was applied to avoid striking the prop on a taxiway light. The left main tire struck the taxi light. As the aircraft began to skid down sloped terrain mixture was set to cut off; right rudder and up elevator was applied to try to prevent a prop strike. The engine stopped before the aircraft stopped moving. The aircraft appeared undamaged. No injury was sustained by pilot or passenger.




Synopsis: GA pilot reported a taxiway excursion while taxiing to Runway 3 at JNX.
Date: 201303
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Saab 340 Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Tires
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Other Person
When detected: In-flight
Result: General Maintenance Action

Narrative: The aircraft was determined to be in good working order. The pre-flight and first flight of the day checks were all normal. We took off and had a routine flight. Upon landing another aircraft that was holding short of the runway told the Tower that the previous landing aircraft looked like it was missing a tire. We were already exiting the runway; and when clear; we stopped the plane. During the roll out we observed the anti-skid annunciator flashing. This sometimes comes on when one side of the plane touches down before the other; so initially we did not think anything was out of the ordinary until we heard the other crew report. The airport authority came over and signaled to us and confirmed that we were missing a tire. I was on the radio with Maintenance Control; Dispatch and Operations trying to make a plan to proceed. After about 25 minutes and Maintenance coming out to the plane; it was determined that we would be towed to the gate.




Synopsis: During landing roll out; the pilots of a Saab 340 heard another crew comment to the Tower Controller that the aircraft that just landed appeared to be missing a tire. It was confirmed by the airport authority that they were missing a tire. They had no previous indication of the condition other than an anti-skid annunciation during roll out.
Date: 201301
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B717 (Formerly MD-95)
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Data Processing
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On arrival at 12;000 MSL we experienced approximately 16 simultaneous Level 3 and 4 alerts. Captain and First Officer PFD DU's did not fail and attitude indication did not fail. Airspeed tape fluctuating wildly from 100 KTS to 500 KTS. Altitude tape fluctuating wildly + and - 2;000 FT. The alerts we could remember are: Stick Pusher Fail; Alternate Trim Fail; Autopilot Fail; Auto Thrust Fail; FCP Fail; Over speed Warning Clacker; Rudder Restricted; CPC Fail; Flight Director Fail; Unable RNP; Intermittent Mode C and TCAS; Brake Pressure Low; Rudder Pitot Fail. Basically we were down to the ISIS [Integrated Standby Instrument System.] No Emergency declared because we did still have control of the aircraft and also in trying to assess which course of action to take; most failures suddenly returned to normal descending through 4;000 FT to 2;000 FT. At that point we could see the airport. Then the multiple alerts and failures started again. Now the first priority was to get the aircraft on the ground. We landed VFR in light snow without incident. It is my understanding that Maintenance basically rebooted the aircraft computers; ran some internal test and returned the aircraft to service. It is my opinion that this aircraft should never have been returned to service in this potentially hazardous condition. If it happened once then it could happen again and next time could result in a life threatening accident. The multiple alerts and aural warnings were almost overwhelming. We worked together using CRM techniques to safely land the airplane.




Synopsis: B717 experienced approximately 16 simultaneous Level 3 and 4 alerts at 12;000 FT during arrival; indicating multiple system failures. The crew was able to continue visually and land at destination safely; although the multiple alerts and aural warnings were described as almost overwhelming.
Date: 201304
Local time of day: 1201-1800
Location: ZID.ARTCC, IN
Aircraft: EMB ERJ 135 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZID
ATC / advisory: Center ZID
Second aircraft: Regional Jet 200 ER/LR (CRJ200)
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Other / Unknown; Communication Breakdown
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: Aircraft X and Y both experienced moderate turbulence and were requesting lower. I called G57 and gave them the information and make my point-out and request for control. The G57 Controller told me that he will have to call me back. You've got be kidding me; this was severe and people are getting hurt while I was waiting for coordination. Recommendation; fix this known problem before something tragic happens.




Synopsis: ZID Controller described an unsafe situation when failing to receive a helpful response from an adjacent facility regarding an immediate request for an altitude change due to turbulence.
Date: 201512
Local time of day: 0601-1200
Location: LVJ.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna Aircraft Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Taxi
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Security; Ground Event / Encounter Person / Animal / Bird
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Airport
Primary problem: Ambiguous

Narrative: On several occasions; I have witnessed near collisions between taxiing aircraft and people (usually kids) on dirt bikes and off-road vehicles on the taxiways and runways at Pearland Regional Airport (LVJ).  The airport is entirely private property and those riding motorcycles and four-wheelers are probably coming in from the surrounding neighborhoods.  Other pilots and I have reported these close calls to airport management and been told that they have no authority over trespassers and have refused to do anything about the danger.  I have tried to talk to the riders to warn them about their behavior; but whenever I approach them; they speed off into the woods in the direction of the adjacent trailer park.  As this problem continues to get worse; I fear that someone will ride into a spinning propeller resulting [in] a damaged airplane and probably a dead child.




Synopsis: A general aviation pilot reported several encounters with vehicles operating near aircraft at Pearland Regional Airport; a privately owned airport. The pilot is concerned for the safety of all persons involved but has been unable to gain the assistance of airport management.