elihoole/asrs-aviation-reports huggingface dataset:
Date: 201311
Local time of day: 0601-1200
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Reverser Cascade
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty); Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Inflight Shutdown; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Captain called me and said we had a situation which was going to require us to land with one engine and at that point I did not need to prepare the cabin for an evacuation. He explained the situation telling me that the left thrust lever was stuck; and that we would be shutting down the left engine in order to land and we may need to divert into another city. He was talking with Dispatch and would call me back about diverting. When he called back we were 20 minutes out and we would be landing at a divert airport. I repeated everything up to this point back to him so he would know that I understood the situation. He then made an announcement to our passengers telling them about the situation. I prepared myself by discreetly retrieving my FAM and the Evacuation Checklist. I read this information in the galley area while I was cleaning up so the passengers would not know what I was doing. I had to be prepared mentally so that if we did have to evacuate I would be ready. I also walked up and down the aisle more than usual so that if the passengers had questions I would be there for them. They were quiet and calm and no one seemed upset about the situation. The Captain and First Officer did a remarkable job landing the plane. It was a normal landing. After landing fire trucks and EMT personnel followed us to the gate.




Synopsis: A CRJ-200 Flight Attendant reported the Captain told her to prepare for an emergency landing; but no evacuation preparation; because an engine with a malfunctioning thrust reverser would be shutdown prior to landing.
Date: 201708
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: 15
Light: Dawn
Aircraft: Global Express (BD700)
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Conflict Airborne Conflict; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We boarded our passengers and contacted departure for our clearance as the local control tower was not yet open. We received our clearance and 'Hold For Release' instructions after several failed attempts due to bad radio reception.We then taxied the aircraft out to the departure end of runway while listening to local traffic advisory frequency. At the departure end we attempted to contact departure several times to obtain our departure clearance and were unable again due to bad reception.It was then that I told my co-pilot that we would and 'pick-it-up' on the go. This was a bad decision on my part as well as not communicating what that meant to my very new co-pilot. We departed VFR and my co-pilot checked in. I heard the confusion while flying yet was busy to avoid [an adjacent airport] as well as keeping eyes on sight of a departing or arriving aircraft and I was maneuvering to avoid any conflict. However the communication was confusion when the controller asked if we were VFR and my copilot was responding 'no we have an IFR'. I was telling my co-pilot 'No; we were Hold For Release' which just added more confusion as he did not understand. This was when I transmitted 'yes; we are VFR'. I was to find out later that there may have been a conflict with traffic on final with an aircraft on long final. I was aware of the long final aircraft and made an immediate right turn on departure.Overall I should had made every effort to call TRACON on the ground first to receive my clearance as well as used better CRM to communicate with my co-pilot.In retrospect as well and in regards to this entire trip and having only 7 days home since its inception. I think there were chain of events relating to Human Performance affecting my bad decision making. I was generally feeling homesick and anxious to get home. I should have recognized this as a senior Pilot early on.


Second narrative: [Narrative contained no additional information.]


Synopsis: BD700 flight crew reported taking off without being released by ATC at an airport with a closed Tower.
Date: 201512
Local time of day: 1201-1800
Location: PDX.Airport, OR
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Descent
Airspace: Class E P80
ATC / advisory: TRACON P80
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Given clearance to descend and maintain what we understood as 3000. We read back 3000 and were not corrected. Upon descent through 3600 ATC advised us that we had descended below their assigned altitude of 5000. At the time of the correction; we climbed to 4000 and continued the approach.




Synopsis: PA28 pilot reports being cleared to descend to 3000 feet by PDX Approach (P80) and reading it back without correction. Passing 3600 feet ATC advised that the clearance was to 5000 feet and to climb back to 4000 feet.
Date: 201710
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Final Approach
Aircraft component: Flap Control (Trailing & Leading Edge)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Workload; Distraction
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Flaps failed to extend. Ran alternate flaps extension checklist. Landed uneventfully.




Synopsis: B737 Captain reported a failure of the flaps to extend normally. An alternate method was used and an uneventful landing was accomplished.
Date: 202108
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Troubleshooting; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed As Precaution; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Procedure; Human Factors; Aircraft
Primary problem: Aircraft

Narrative: During cruise at 7;500 feet  MSL with a properly leaned engine and (nearly) full fuel; the engine on the aircraft suddenly lost power.  The engine struggled to maintain idle speed at full power.  I [requested priority handling] when the fuel controls (mixture and throttle) were checked and the problem persisted.  When enroute to the closest landing location it was found that the engine could be coaxed to approx 2/3 power by pumping the throttle in and out.  Upon landing; a mechanic looked over the fuel system (to include sumps and fuel strainer) but found no issues.  During a subsequent run-up; the engine performed as expected without issue.  When the in-air engine issue occurred the outside air temperature was noted to be approximately 45 degrees.  Based upon the lack of issues found with the fuel system; the subsequent successful run-up and the noted temperature; it is believed that the aircraft experienced carb-icing which caused the issue.  After review with the mechanic; the aircraft was returned to service.  No damage or injury was experienced as a result of this issue. Approach was notified via the approach frequency when the aircraft successfully landed and no subsequent actions/communication was requested.




Synopsis: C172 pilot reported loss of engine power and requested priority handling to expedite arrival at destination airport.
Date: 201411
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Rudder Control System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: First Officer (FO) was pilot flying.  During takeoff from [at] approximately 80K; FO asked if I was on rudder pedals.  I told him no as he was attempting to put in right rudder to keep airplane on runway centerline.  Aircraft remained on centerline.  We were then going through approximately 120 knots when he said 'Something does not feel right in rudder'  At this point I elected to continue takeoff as we were rapidly approaching V1.  We took off and continued with climbout and cleaned the airplane up.  He said he had [to] 'muscle' the right rudder pedal to keep airplane on centerline.  He said he felt as if there was no hydraulic assist in the rudders.  He asked me to 'feel' the aircraft.  I took control and the rudder felt very heavy.  I then engaged the autopilot and gave the FO back the aircraft.  We leveled off at 11000 FT to trouble shoot.  FO continued to fly the aircraft....  I went to QRH to look for assistance on rudder problems.  Nothing was found for that problem.  Contacted dispatch through Commercial Radio and also tried to consult with  Maintenance Control.  At that low altitude; it was almost impossible to talk with either over Commercial Radio.  We advised them we were going to return to [our departure aiport].  As we had a flight control problem; we declared and emergency with ATC; requested return vectors and requested ARFF.  We landed...overweight.  The landing was normal [with] a minimal sink rate.  We taxied off runway uneventfully and [taxied to the gate.]




Synopsis: A B737 flight crew declared an emergency and returned to their departure airport when the right rudder pedal was heavy and input unresponsive.
Date: 201905
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Thunderstorm
Light: Daylight
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Fatigue; Distraction; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Staffing; Weather; Human Factors; Company Policy
Primary problem: Human Factors

Narrative: Due to weather enroute and airport congestion; we were less than 15 minutes from CCO (Critical Crew Off time) on originating flight. Late to ZZZ1; fatiguing without [Relief Pilot]. On departure; fuel critical. Waited 45 minutes for final weights. Only resolved after 2 calls to Dispatch. Even with one engine shutdown (one stayed running for taxi) we were in jeopardy of returning to the gate for fuel or missing CCO. Now already over 8:00 block with no [Relief Pilot].  Slightly higher fuel burn than on [Forecast]. Re-routed for thunderstorms over ZZZ.  Routed down [the] coast then back west.  ATC was great getting planes around the storms to west of ZZZ.  Other flights diverting; our bingo was 10.0 with ZZZ2 [as] our divert.  ZZZ now VFR; we had field in sight; fuel now less than 10.0.  Slam dunk into XXR; runway changed due to other lower fuel aircraft getting priority.  Did not realize we did not do the Landing Checklist until touchdown. Obviously gear and flaps were in the proper position.




Synopsis: B757 Captain reported that due to several route changes in flight; flight crew failed to perform the Landing Checklist.
Date: 201909
Location: ASH.Airport, NH
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Mission: Training
Flight phase: Parked
Second aircraft: Skyhawk 172/Cutlass 172
Aircraft component: Attitude Indicator(Gyro/Horizon/ADI)
Component problem: Failed
Reporter organization: Personal
Reporter qualification: Flight Crew Private; Flight Crew Instrument; Flight Crew Student
Human factors: Situational Awareness; Training / Qualification; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR
Detector: Person Other Person
When detected: Routine Inspection
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Aircraft; Company Policy; Human Factors
Primary problem: Company Policy

Narrative: The flight school portion of my school is done through [FBO]. [FBO] has had 3 engine failures in the past 2 months and 2 airplanes that are currently flying in an unsafe condition. Aircraft X has an attitude indicator with more than 30 degrees of error and is not marked INOP and I believe it possible that it was taken IFR in this condition. Yesterday Aircraft Y had an almost snapped alternator belt; and the airplane had just come out of an inspection. There is a picture of the belt and the student that was supposed to fly the aircraft claimed that someone in maintenance suggested the plane would be fine to be used. I cannot prove any one incidents but I believe there are more issues to be looked into. I believe an inspection of these airplanes would be a good action to correct these issues. This is a part 141 flight program and I am unsure where these problems should be reported. If this is the wrong place or if these concerns are not serious; feel free to disregard this report.




Synopsis: A student at a flight school reported that the school's aircraft are not maintained in a safe condition.
Date: 201904
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Ferry / Re-Positioning
Flight phase: Landing
Aircraft component: Propeller Blade
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Distraction; Situational Awareness
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: After making a low approach; I set the aircraft up for landing on a private paved.  After touching down; I was scanning the area for wildlife and did not realize that while distracted I had departed the runway.  I quickly attempted to regain control of the aircraft and return it to the airplane but not before the nose gear hit uneven terrain resulting in a propeller strike.  Other than the aircraft; there was no damage to any other property.




Synopsis: SR22 pilot reported a runway excursion during landing resulting in a damaged propeller.
Date: 201709
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Situational Awareness; Communication Breakdown
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: The aircraft began to move while parked at the gate without the intent of it moving. It was rolling toward the jet bridge and ground equipment. The parking brake had been released in preparation for the aircraft to be pulled into the [tug]. The ground crew removed the chocks without the [tug] in position and the aircraft began to roll toward the [tug]. We noticed aircraft movement and another ground crew knocked on the side of the aircraft. I quickly stepped on the brakes and the aircraft stopped.The ground crew did not communicate that they were removing the chocks. We had not yet run any checklists and there was no hydraulic power yet on the aircraft. The cause of the event was the ground crew removing the chocks without any communication with the flight deck. We were fortunate that the brake accumulators had enough pressure remaining to stop the aircraft. It was apparent that the ground crew individual who removed the chocks was unaware of the possible consequences of their actions. The other ground crew individual; the one who knocked on the side of the aircraft; was also instructing the unaware person to move the [tug] out of the way. It appeared that they were training the other individual.


Second narrative: Just closed the main cabin door and released the parking brake to record the time for ACARS to meet a minimum turn time for an on time departure for a ferry flight. This is a common practice and within normal operating standards to release the brake after the door closes. Both pilots were heads down confirming routing entered in the FMS for the upcoming flight and reviewing the weather for departure. The aircraft started slowly moving forward and when both pilots looked outside. It appeared as if the ground crew was pulling the aircraft into the pushback tug to capture the nose wheel as is also common practice. However neither of the pilots gave any brake release signal; or chocks out signal; verbal or non-verbal to the ground crew.


Synopsis: CRJ-700 flight crew reported that their aircraft started rolling forward at the gate when ramp personnel removed the chocks without informing the flight crew.
Date: 202009
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Bell Helicopter 407
Operator: Government
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Main Rotor Blade
Reporter organization: Government
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial
Human factors: Confusion; Distraction
Second reporter function: Pilot Flying; Instructor
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition; Flight Crew Regained Aircraft Control; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Procedure

Narrative: I was conducting flight training with an instructor at ZZZ. The Bell 407 I was operating experienced contact between the main rotor and tail rotor drive shaft. The drive shaft was sheared after the helicopter was on the ground. The tower was notified and the aircraft was subsequently towed to hanger.


Second narrative: While conducting autorotation training in a Bell-407 helicopter at ZZZ; I experienced a main rotor contact with the tail rotor driveshaft. The tail drive shaft sheared while on the ground at low rotor RPM. No injuries were sustained. Tower was notified and the helicopter was towed to a hangar. The FAA examined the helicopter; and the crew are scheduled to speak with the FAA.


Synopsis: Bell 407 Instructor reported rotor blades contacting tail rotor shaft during training.