elihoole/asrs-aviation-reports huggingface dataset:
Date: 201903
Local time of day: 1801-2400
Aircraft: Helicopter
Operator: Air Taxi
Operating under: Part 135
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Taxi
Reporter function: Lead Technician
Reporter qualification: Maintenance Inspection Authority
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Other maint completion
Result: General None Reported / Taken
Contributing factors: Aircraft; Company Policy; Procedure
Primary problem: Company Policy

Narrative: The aircraft was in the final steps of troubleshooting and testing on an upgraded Sat Com (Satellite Communication) system with a micro flight data recorder feature. This system was installed as a replacement to a prior system to meet the requirements of FAR Part 135.607 for Air Ambulance Operations. The interior was in a state of removal with wire harnesses and connectors in final assembly. Management informed us that the aircraft was needed for a flight in 3 hrs as they had scheduled three med team transport with only two other aircraft available. Management was advised that reassembly and a ground / flight test were required by the Sat Com STC (Supplemental Type Certificate) instructions to perform an 'EMI (Electromagnetic Interference) test' and operational check of the system. It was decided to reinstall the interior and do the testing prior to use as an 'air ambulance'. I generated a log entry for the purpose of the maintenance check flight with the system operational to document the required ground and inflight test procedures. I returned to the aircraft and was informed that the flight for the med team flight had been moved up and there was not enough time for the test. It would have to be completed on the next day. I secured power to the sat com system by zip tying the circuit breaker in a deactivated position.The consequences of the flight; the aircraft did not meet the Part 135 Air Ambulance requirement by the flight data recorder system being inop. Management was aware of this; but continue to operate the aircraft in this configuration.




Synopsis: Maintenance Technician reported that aircraft was operated without legally required flight data recorder.
Date: 202104
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: After landing in ZZZ; Runway XX. The taxi instructions were; 2 rights; cross [Runway] XY-L; ... to the gate. Captain got distracted by a taxi light not being well lit (which interrupted his after landing flow).I was doing the after landing flow and my Jeppesen 10-9 page froze. By the time I looked up; the Captain made the two right turns but it was onto the option portion of taxiway; [X]; which was closed. Captain attempted a 180 turn and it didn't work out. Had to coordinate with Operations to get a tug to come out and move the aircraft. No damage occurred and the aircraft was able to safely taxi to the gate.


Second narrative: During descent; I misunderstood which taxiway portions were open. After FO (First Officer) made his Approach Brief; in which he included exiting at [Taxiway] X to join [Taxiway] Y; I interjected that I would prefer that he plan his exit one exit prior to as that would be the easier crossing to the gate. This developed a bias in my mind. Furthermore; the FO must not have had a grasp of my intentions and that I was unclear that X east of west was closed.As I joined X; I saw the barricades and stopped. I spoke with ATC. They suggested and I attempted a 180 degree turn. I stopped about 100 degrees into the turn and set the parking brake. At all times I was on taxiways that were open. I asked for a tug and Ground Crew to reposition the aircraft. Once aircraft was facing opposite direction; I taxied to the gate via assigned taxi clearance. No damage occurred to the aircraft.


Synopsis: B737 flight crew reported taking a wrong turn during taxi in that required repositioning by a tug.
Date: 202005
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Weather elements / visibility: Turbulence; 10
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Flight Engineer; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Confusion; Training / Qualification; Human-Machine Interface
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Became Reoriented; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: I was on a vector with ZZZ approach for a visual to Runway XX and a descent clearance to 3;000 MSL.  Passing through 3;000 the altitude alert flashed and I thought it was a 1;000 foot warning.  At 2;600 MSL I realized my mistake and made an immediate climb back to 3;000 MSL.  Approach made no mention of my deviation and a few minutes later cleared me for the visual to Runway XX.There were a few factors involved. The attitude indicator and heading indicator had been recently replaced with two glass displays.  Though I had flown plenty of glass in the past; these instruments are still somewhat new to me. I had also taken time off earlier in the year and combined with COVID-19 had not done any flying.  I had planned on going out with an instructor before the flight; but the social distancing with COVID-19 made me decide against doing that. I made a few flights totaling 7 hours during a two week period before the date of the incident by myself doing basic and commercial air work; takeoffs and landings and just getting familiar with the plane again.  In March I also did several approaches and holds in a flight simulator. The simulator was configured with a standard six pack.No excuses on my part.  I momentarily got behind the airplane and had some confusion with what one of my instruments was telling me.




Synopsis: GA pilot reported misinterpreting an altitude alert and descended from assigned altitude while on approach. Lack of familiarity with the instrument panel and lack of recent flying due to the COVID-19 pandemic were cited as contributing factors.
Date: 202005
Local time of day: 0601-1200
Location: JAN.Airport, MS
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Cruise
Airspace: Class C JAN
ATC / advisory: Tower JAN
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Air Traffic Control Fully Certified; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Airport; Chart Or Publication; Company Policy
Primary problem: Chart Or Publication

Narrative: During a training session; I asked the student to show me the NOTAM that indicated Runway 34L/16R was closed. There were NOTAMs showing all the lights and approaches inoperative but nothing that advised the runway was closed. We used the Foreflight and EFB (electronic flight bag) programs to search NOTAMs. Researched the FAA FNS NOTAM search page. I found an 'On Airport Construction Graphic' which showed the closed parts of the airfield using an airport taxi-diagram but there was no textual NOTAM showing the current aerodrome status reference closed runways and taxiways. This is a critical flight safety matter and must be addressed immediately!




Synopsis: Flight instructor reported there was no NOTAM for a runway closure at JAN airport.
Date: 202011
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Human factors: Communication Breakdown
Anomaly: Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: I was briefing the over-wing window exit as the C Flight Attendant with my safety information card in hand. When I asked the gentleman in the two-seater if he was willing and able to sit in the exit row and ask for a verbal confirmation he asked for water.I told him no sir I was asking him if he was willing and able to sit in the exit row he said yeah. He said do you want me to move? I said no you're fine I just wanna make sure that you're aware that you're in the exit row. And that was it.I don't know if you could not hear me because of the mask. Or I was speaking too fast. Or not clearly enough for him. I will need to work on that.




Synopsis: Flight Attendant reported that communication with a passenger regarding exit row seating may have been misheard due to speaking through a face mask.
Date: 201512
Local time of day: 1201-1800
Location: DCA.Airport, DC
Light: Dusk
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi; Initial Climb; Takeoff / Launch
Airspace: Class B DCA
ATC / advisory: TRACON PCT; Tower DCA
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Distraction; Situational Awareness; Workload; Time Pressure
Second reporter function: Captain; Pilot Not Flying
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight; Taxi
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Company Policy; Human Factors
Primary problem: Human Factors

Narrative: We were operating [Flight ABCD].  I had obtained my clearance via the ACARS PDC; which gave us the squawk code and flight number and assigned route.  I contacted ground using the correct call sign and ground responded with the incorrect call sign; but I did not think anything of it because it was a quick taxi and we were switched over to tower.  We had to run the Runway SID change checklist.  Tower asked us if we were ready and we responded with that we needed a few minutes to run a checklist.  I remember being confused because tower was calling us by the wrong flight number.  After running the checklist we contacted tower and told them we were ready.  The controller used the wrong flight number again and we attempted to correct him with emphasis on our flight number.  I did mention this to the Captain and he told the controller very plainly that we were [Flight ABCD].  Then the controller messed up the call sign again and cleared us for takeoff.  Once we were airborne Departure Control told us that [Flight ABCD] was not an active flight and all they had on file was a [Flight ABDD]. ATC instructed us to change our call signs and squawk code. ATC was expecting us to use the flight plan for [ABDD]; but we did not have that information because we had [ABCD] clearance.Due to this confusion we should have corrected the call sign before takeoff.


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


Synopsis: There was confusion over a flight number at DCA. ATC was using one flight number and the crew had a different; similar flight number; but did not clarify ATC's mistake until after takeoff.
Date: 201210
Local time of day: 1201-1800
Location: EUG.Airport, OR
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight phase: Initial Approach
Airspace: Class E EUG
ATC / advisory: TRACON EUG
Aircraft component: TCAS Equipment
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Took Evasive Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At 4;000 FT and just as we are handed off from Cascade Approach to Tower I noticed that a blue dot showing a 0 on my TCAS had popped up from no where. I looked outside to see if I could see anything since there was no traffic reported by Approach or that we never had an aircraft on the TCAS on our descent. From the time it took for me to register that something was on the TCAS we got a RA to climb. I followed the guidance to climb. After a few seconds the RA stopped and there was no longer anything on our TCAS. I notified Cascade Approach since we never went to Tower. We climbed about 1;500 FT on our maneuver. Cascade said they showed no aircraft on their radar. We were vectored back to final and given a phone number to call. We had no other problems on approach. After getting to the gate and finishing the check list. I call Cascade and talked to the supervisor. He said he was standing next to the Controller as soon as he told him we were complying with the RA. He too said that he saw nothing on the screen. I told him we didn't see anything either but had to comply. He stated he was going to submit his report and I said the same. I can only guess it was a glitch in the TCAS system since we never saw the aircraft in question and that it popped right on the screen from no where.




Synopsis: Air Carrier Captain describes the sudden appearance of a TCAS target; followed quickly by a RA to climb. ATC is advised and the target suddenly disappears after climbing 1;500 FT. ATC never had a target on Radar and the crew never had a visual sighting.
Date: 201407
Local time of day: 0001-0600
Location: ONT.Airport, CA
Flight conditions: VMC
Light: Dawn
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ONT
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were given a taxi clearance to taxi from the ramp to Runway 26L via Taxiway Uniform and Sierra to Runway 26L; and to hold short of Taxiway Delta. The taxi instructions from the Ground Controller were out of the normal sequence and we were confused because Taxiway Delta is at the departure end of Runway 8R; not 26L.   The First Officer attempted to verify the clearance with the Controller several times and she was becoming increasingly agitated; and twice told us to read back the runway assignment with our call sign which we did. Because we were still unsure what she wanted us to do; we stopped the aircraft on Taxiway Uniform short of Runway 26L trying to get some clarification. As we were sitting there; a smaller aircraft with another carrier's colors departed Runway 8R in front of us. Had we not stopped; we would have been crossing the runway with that aircraft on takeoff roll. As that was happening; the First Officer pointed out to the Controller that Taxiway Delta was at the departure end of Runway 8R and we were then cleared to taxi to Runway 26L and hold short of Taxiway Whiskey. Neither the First Officer nor I ever heard instructions to hold short of any runways off Taxiway Whiskey. Neither the First Officer nor I ever heard instructions to hold short of any runways.




Synopsis: Pilot departing ONT is given terrible taxi instruction to Runway 26L. Controller is questioned; agitated because of the questions. While holding short of 26L; an aircraft departs in front of the taxing aircraft which had no hold short instructions.
Date: 202001
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Second reporter function: Pilot Flying; First Officer
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: During takeoff noticed [a] strong 'dirty sock' smell. Donned oxygen masks. Confirmed with flight attendants that smell was present throughout cabin. Advised ATC and returned to ZZZ. After blocking in; ZZZ Maintenance told us; that they had done an engine wash the previous night. We were the first departure afterwards. Re-examine the engine wash procedure. This was my second odor and fumes event after an engine wash. Both ended in priority returns to the departure airport. The pack burn after an engine wash is apparently done at 70% power. Takeoff power is much higher!


Second narrative: Departing ZZZ; Captain noticed an acrid odor and verified with First Officer and cabin crew. Advised with ATC and returned to ZZZ. Maintenance confirmed an engine wash was completed overnight prior to this first launch of the day. Odor in cabin. Review maintenance procedures for pack burn after engine wash.


Synopsis: B737-800 flight crew and Flight Attendant reported a 'dirty socks; musty' odor during takeoff and executed an air return.
Date: 201402
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: Rain
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Flight phase: Parked
Aircraft component: External Power
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel; Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Equipment / Tooling
Primary problem: Ambiguous

Narrative: While deplaning at the gate; ramp personal plugged external power into the aircraft. Pilots heard a loud banging noise and followed by a burnt electrical smell. The First Officer and I both opened our windows to evaluate the situation. I told ramp to immediately disconnect the external power. He replied it is already disconnected. I noticed a Maintenance Technician already waiting at the gate; when we arrived. He immediately inspected aircraft. Pilots later noticed some smoke enter flight deck; either through First Officer's open window or right side floor panels. Maintenance opened E and E compartment and reported no fire. I confirmed no fire with Maintenance and verbally with Mechanic. I made a log book write up and aircraft was removed from service.


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


Synopsis: B737 flight crew reports a loud banging noise and electrical fumes as ground power is connected to the aircraft at the gate. Ground power is quickly disconnected and the aircraft is taken out of service for maintenance.
Date: 202002
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Aircraft component: Powerplant Fuel Control Unit
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance; Person Other Person
When detected: Other Next day
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was assigned to remove and replace a fuel flow governor on aircraft's #2 engine. I was the Mechanic and another Mechanic was [performing] the RII (Required Inspection Item). I [later] became aware that the Mechanic who performed the RII was not certified on B-757 aircraft. I notified my Supervisor and aircraft Maintenance Control immediately and the aircraft was taken out of service.




Synopsis: B757 Airline Mechanic reported a procedural violation regarding a non qualified technician performing maintenance on aircraft.
Date: 201510
Local time of day: 1201-1800
Location: BWG.Airport, KY
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class G BWG
ATC / advisory: CTAF BWG
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: [Weekday] evening while on active run way (03-21) after making all the calls from pre taxiing to entering runway and call for departing and was already rolling on runway 3 departing; Aircraft Y which was taxing on (non-active runway 12-30) failed to stop and crossed runway 3-21 just few inches in-front of me causing me to pull up and missing collision. There were multiple witness during this incident of intersection runway incursion missed collision.




Synopsis: A pilot took evasive action from an aircraft taxiing on a crossing runway while taking off on CTAF BWG Runway 3.