elihoole/asrs-aviation-reports huggingface dataset:
Date: 201603
Location: ZZZ.Airport, US
Aircraft: Q400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pressurization Control System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Distraction; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: Departed runway; VMC climb clearance; Maximum Takeoff Power (MTOP) and bleeds off for performance due to weight. Complicated procedure requiring a lot of attention and precision flying. Forgot to turn bleeds on. At approximately 9;500 feet master warning cabin pressure warning illuminated. Donned mask and immediately turned on bleeds. Called for the checklist to cover all bases even though I knew we got the warning because the bleeds were off. While going through the checklist we noticed that the cabin was remaining at a steady 9;500 feet pressure altitude and would not pressurize. As a result the cabin press warning light remained illuminated. Completed cabin pressure checklist which directed us to the pressurization fail checklist. The pressurization fail checklist eventually had us switch the pressurization mode to Manual. Once in Manual mode we were finally able to control the cabin pressure. We decreased the cabin altitude and the cabin pressure warning light extinguished. Not sure why it would not pressurize in Auto mode. Completed the manual pressurization control checklist. Once pressurization was normalized removed O2 masks; climbed up to altitude and continued our flight as normal. Once stabilized in cruise called Maintenance Control and advised them about what happened.[The cause was] workload saturation and distractions like the gear warning horn going off non-stop and flying close to terrain. Malfunction of the pressurization Auto mode.




Synopsis: Q400 Captain reported experiencing loss of cabin pressure resulting from flight crew failure to turn engine bleed switches on following a special takeoff procedure. Recovery from this error was compounded by malfunction of the pressurization auto mode.
Date: 201701
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
Aircraft component: Wing Access Panel
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Passenger
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: A deplaning passenger came up to me and showed me a picture of the Left Hand wing with a panel floating while in flight. He said you can't see it on the ground. I saw all; over 20 screws; missing from the panel. I entered the discrepancy in the logbook.




Synopsis: A319 Captain reported that a passenger told him that a panel on top of the left hand wing was not secured.
Date: 202112
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna Aircraft Undifferentiated or Other Model
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Initial Climb
Airspace: Class E ZZZ1
ATC / advisory: UNICOM ZZZ
Second aircraft: Cessna Aircraft Undifferentiated or Other Model
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Workload; Training / Qualification; Confusion
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure; Airport
Primary problem: Human Factors

Narrative: There was several of us in the pattern doing touch and goes with our students. I was with my student landing/taking off Runway XX at ZZZ; when we got a radio call on frequency that stated '10 mile final Runway XY.' Another pilot in the pattern replied back we were all using Runway XX and there was several of us in the pattern. The pilot on final then said he would switch to Runway XX. I then stated we were on upwind. We were around 300 ft. and I noticed his aircraft  straight in front of us slightly to the right; coming in extremely fast and extremely close to us. At this point I could not turn right and get out of the pattern as he was slightly to the right and I believe I would have had a mid air. I then made the decision to do a climbing left turn. As I was doing a climbing left turn he turned slightly right and nearly had another midair with him he was about 50 to 100 ft. from me. I finally got safe away from him. Another pilot in the pattern made a radio call to him; and then I made a radio call to him when I was at a safe altitude and distance; he then stated he did not see my aircraft.




Synopsis: Flight Instructor reported a NMAC with another aircraft entering the pattern.
Date: 201406
Local time of day: 0601-1200
Location: PHF.Airport, VA
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Flight phase: Taxi
ATC / advisory: CTAF PHF
Reporter organization: Government
Reporter function: Other / Unknown
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Second reporter function: Other / Unknown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Before opening; a tug announced himself on 118.7; that he was transitioning north on Runway 2 with aircraft in tow.  Aircraft X announced that he was taxiing out on taxiway a for a Runway 20 departure.  The tug re-announced that he was on Runway 2 and that his intentions were to turn off at Taxiway C.  Aircraft X then announced that he was departing Runway 20 and started rolling.  The tug promptly exited Runway 2 on Taxiway D when a controller in the Tower keyed in on 118.7 and told Aircraft X to stop.  Aircraft X stopped his roll and back taxied Runway 20 for another departure attempt; while the tug held short of Runway 20 on Taxiway D.  Aircraft X claimed to not have heard the tugs announcements on 118.7 until the incident already occurred.  After aircraft X departed; the tug continued to the ramp without further incident.  No vehicles or aircraft were damaged during this.   Incident occurred prior to opening.  Aircraft and vehicles understand that they move at their own risk.


Second narrative: Arrived in Tower to perform opening duties.  Monitored frequencies.  Heard a tug call on 118.7 that he was taxiing onto Runway 7 to Runway 2 to taxi to a ramp from a hangar.  Observed the tug on Runway 2. The tug reported on Runway 2.  Aircraft X called on 118.7 reporting taxing from back ramp to Runway 20.  I observed Aircraft X taxiing to Runway 20.  Aircraft X reported takeoff of Runway 20 while the tug was taxing northbound on Runway 20.Review procedures for CTAF with pilots.


Synopsis: PHF controllers describes situation where a tug is reporting its position on the runway; while an aircraft attempts to depart.  Tower Controller uses radio and tells departing aircraft to stop.  Tower is not open when this happens.
Date: 201605
Local time of day: 0001-0600
Location: JNU.Airport, AK
Aircraft: Beaver DHC-2
Flight plan: VFR
Flight phase: Descent
Airspace: Class E ZAN
ATC / advisory: Tower JNU
Second aircraft: Cessna 150
Reporter organization: Government
Reporter function: Local
Human factors: Distraction; Workload
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure; Aircraft
Primary problem: Human Factors

Narrative: A C150 departed as I took Local one. He was slow and outbound for outer point. A DHC2 called inbound for a straight in. I noticed an IFR strip for a Learjet on a Visual approach. He was only seven miles from the field. Much closer than he should have been without being switched to Juneau tower. In addition; he was at 10000 feet. When he finally came over I was expecting a possible go around and handling an unusual situation with an IFR aircraft. At the same time the DHC2 called inbound from outer point. By the time I got back to the Cessna and gave traffic on the DHC2; the Cessna said he saw him and was passed him. All aircraft landed without incident upon arrival the DHC2 was rolling out in the water lane and the pilot said; 'hey tower I saw that Cessna as he passed my windshield.' The Cessna was not equipped with a transponder. It was outside my class Delta airspace and I was handling an unusual situation with an IFR Learjet. The pilot called and complained on the traffic call and a newly certified CIC took the call. The CIC mistakenly checked significant and filed as an NMAC instead of public inquiry. It was two VFR airplanes outside my airspace and I was giving priority handling to an IFR aircraft.




Synopsis: JNU Tower Controller was informed of an NMAC between a DHC2 landing on the water lane and a C150 that had departed opposite direction a few minutes earlier from the paved runway. Both aircraft were VFR and the C150 was not transponder equipped.
Date: 201807
Local time of day: 0601-1200
Location: KZAK.ARTCC, HI
Flight conditions: VMC
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent; Landing
ATC / advisory: Center KZAK
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Distraction; Situational Awareness
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Executed Go Around / Missed Approach; General Flight Cancelled / Delayed
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The weather was clear; and my First Officer and I were having a conversation as we passed through 10;000 ft MSL. I turned on the sterile cockpit light; but did not cease the conversation as I should have.We had been cleared for the approach; and everything was set up for the RNAV P 24R; when I noticed that I was rapidly approaching the final approach fix; and I hadn't begun configuring the aircraft for landing. We were slow enough to call for flaps 1; flaps 5 and gear down; but as we began to descend on the glide path (and I was able to call for flaps 15) we had trouble slowing below 180 kias.I believe we were between 600 and 800 ft when I initiated the go-around. I pushed TOGA (Take-Off / Go-Around); and made the initial call outs through flaps 15; but then focused on what the tower was telling us to do instead of continuing to focus on the configuration of the aircraft.The flaps 15 placard speed was exceeded. The FO (First Officer) called it out; and the flaps were retracted; but not in time to avoid an overspeed of flaps 1 as they were retracting to flaps up.We were vectored to the northeast for another approach; which; along with the landing was completed uneventfully.Upon completion of the parking checklist; we thoroughly debriefed the event; and concluded that we needed to inform maintenance of the overspeed. At that point; a mechanic met the airplane; and I told him what happened. He acknowledged and thanked me for the information.




Synopsis: Air Carrier Captain reported an unstable approach; missed approach; and flap overspeed.
Date: 201408
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
ATC / advisory: TRACON ZZZ
Aircraft component: Elevator Tab
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 Less Severe
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climb out cabin crew reported abnormal vibrations in the aft part of the cabin. FO (PF) also observed vibration in the control column at the same time. Declared an emergency; completed the Elevator Tab Vibration checklist and returned. Completed logbook entry.




Synopsis: B737-800 pilot experiences abnormal vibrations from the tail of the aircraft which can also be felt in the control column. Crew elects to return to the departure airport.
Date: 201310
Local time of day: 0001-0600
Location: ZMA.ARTCC, FL
Aircraft: Gulfstream III (G1159A)
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZMA
ATC / advisory: Center ZMA
Reporter organization: Government
Reporter function: Enroute
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
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Gulfstream 3 coordinated with MTPP (Haiti) at FL410. The aircraft's time and altitude checked and RADAR service was terminated. After the communication change; Gulfstream 3 appeared to be headed to MUHA airspace (HAV). The D-Side called MTPP to inquire as to why the aircraft may be turning. Meanwhile I was able to reach Gulfstream 3 on guard and he relayed to me that MTPP gave him permission to deviate. The D-Side confirmed what the pilot stated. MTPP when questioned said that they would point Gulfstream 3 to MUHA. It appears that all of the International incidents that are submitted go somewhere and are never heard from again. Working with six foreign facilities daily there are many systemic problems that we encounter but there is very little feedback from any office as to what was the end result of this incident. I would like to follow this incident from ZMA to the dark place that it goes. I am available anytime and authorize the release of this information.




Synopsis: ZMA Controller described a developing conflict event involving several adjacent foreign ATC facilities; the reporter commenting that this; and other events; produce little or no following up information from/to anyone.
Date: 201410
Local time of day: 1201-1800
Location: ZDV.ARTCC, CO
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZDV
ATC / advisory: Center ZDV
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Communication Breakdown; Confusion
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic
Contributing factors: Procedure
Primary problem: Procedure

Narrative: I was working all of our airspace combined up (mid configuration) as I was splitting the airspace off and doing a briefing I noticed a code come off GJT which was Aircraft X.  Denver TRACON normally takes the airspace around 1200Z (0600L) but they never called today.  I called tower and questioned them about the release and they said approach was open; which I told them they never called us to get the airspace.  I then called Denver TRACON who would normally take the airspace and questioned what Aircraft X was doing in my airspace and what was going on because they never called us for the airspace.  The controller said he forgot to call me for the airspace and he did have Aircraft X climbing to 140.  I then released the airspace to them.This is now the second time in a year I have had this happen to me.  I believe a review of their opening checklist may be in order; they need to call and get the airspace before clearing aircraft into it.




Synopsis: ZDV Controller reports of the TRACON not making the morning call to receive a briefing and accept the airspace that was given to the Center the night before.  An aircraft was released into his airspace without his knowledge.
Date: 201701
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Time Pressure
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: We departed the gate on time; and elected to not start the number 2 engine until we had a better idea of takeoff time. We briefed the expected taxi out and were given a taxi clearance slightly different than expected. Shortly after we began taxi; Captain (CA) ordered start of Number 2 engine. I initiated the engine start; and while the engine was starting; we were told to cross the runway and monitor tower. As we crossed the runway; I switched to tower frequency and immediately was told we were next for takeoff and shortly after cleared us to line up and wait with aircraft on 5 mile final. The CA stated that he was unsure of where the taxi line was in relation to 'the block' as there was another aircraft in the block. I looked up to assist; got distracted from my duties; and did not complete the after engine start flow (APU bleed off; APU off; GEN 2 on; PACK 2 on; the before takeoff checklist was completed. At that point; we were advised there was an aircraft on 2.5 mile final. After takeoff; once established on the RNAV SID; I realized my error and advised the CA before turning on generator; pack; and shutting off APU.


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


Synopsis: A319 flight crew reported being rushed during takeoff resulting in the non-completion of the post engine start checklist.
Date: 201508
Weather elements / visibility: Hail
Light: Night
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)
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness
Anomaly: Flight Deck / Cabin / Aircraft Event Other / Unknown; Ground Event / Encounter Other / Unknown
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors; Weather
Primary problem: Ambiguous

Narrative: Sky was black when we landed. During deplaning the aircraft was hit with 70 mph winds and large hail.  The aircraft was knocked off its blocks and slammed into the jetway.  In the tail; [there] were the remaining PAXs and two flight attendants.  The aircraft tail was lifted up and moved around violently.  My flying partner and I yelled to leave your bags and try to make it off the aircraft. Customer Service agent would not allow PAXs to get off because of a 5 inch gap between aircraft and jetway. PAXs on other flights informed me attendants screamed to sit down and refasten seatbelts and they also slammed jetway and were trapped on aircraft.  Slides are not useable in winds this strong.




Synopsis: Air carrier Flight Attendant describes a high wind event while deplaning passengers at the gate. With most of the passengers off; the tail of the aircraft is violently buffeted by the wind but the Customer Service agent would not allow the remaining passengers off due to the gap that had developed between the aircraft and the jet bridge.
Date: 201605
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Initial cross-country solo. Conducted thorough preflight; including inspection of fuel tanks; fuel sump; and oil levels. No issues observed. Conducted full-power lean and run-up before takeoff- normal magneto drop and carb heat drop. Departed and headed straight to the transition. Frequency change approved approximately 3 miles out; contacted approach and received squawk code. At approximately 3800-4000 msl; engine began running very rough and experienced loss of approx. 200 rpm. Heavy vibrations from engine; visible shaking from cowling; and very loud popping sounds from engine.Immediately changed course back contacted tower; informing them of current situation.  Tower cleared me for left base for Runway XX. Intermittent roughness and occasional temporary rpm drops of up to 50 rpm continued until shutdown; especially at high power settings. Taxi back to parking under own power- informed tower further assistance was not required. Preformed standard shut down; experienced a slight burning odor from the engine.




Synopsis: C172 student pilot experienced a partial power loss while climbing out. They returned to the departure airport and landed without incident.