elihoole/asrs-aviation-reports huggingface dataset:
Date: 201902
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Light: Daylight
Aircraft: SA-227 AC Metro III
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Inverter
Component problem: Failed
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Confusion; Troubleshooting; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Aircraft; Company Policy; Human Factors
Primary problem: Aircraft

Narrative: At the time of the event; the FO (First Officer) was the pilot flying; we were cleared for the ILS approach; were on localizer; and were descending to 2400. Right before the FAF (Final Approach Fix); we both heard a 'pop.' The FO's attitude indicator was flagged; as was the pilot's attitude indicator. At first; we thought circuit breakers had popped; so we looked and saw none popped. A second later; we saw L AC BUS and R AC BUS illuminated; so that meant Inverter #1 had failed. The Captain took control of the aircraft; and we switched to the #2 Inverter. The attitude indicator indicated 'GYRO COMPUTER' for 5-10 seconds before those flags went away; and unfortunately; I drifted off of localizer and got to 3/4 deflection. As I was correcting; Tower called to inform us we were off course. I told them we had an inverter failure; switched to our 2nd inverter; and were correcting. They asked if we wanted vectors; and I said; 'I'm on localizer now; is that what you're showing?' She confirmed I was on localizer. We then landed.It was a system failure which caused me to drift off localizer. In the future; I will ask for vectors and go around. As for the plane; in my opinion; the root cause has not been identified; because this is the fourth Inverter #1 failure in about a month.




Synopsis: SA227 Captain reported an inverter failure on final approach causing them to deviate from the localizer on the ILS.
Date: 201408
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Aeronca Champion
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Landing Gear
Component problem: Failed
Reporter organization: Personal
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew; Person Observer
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Aircraft departed for local flight and it was observed from ground by local pilots that the landing gear was collapsed to centerline under the aircraft and not in a position for a normal landing. Pilot was radioed of the situation and elected to land in the grassy area parallel to the active runway. Under control; the gear collapsed and the right gear separated from the undercarriage. The aircraft continued on the grass till coming to rest upright. The pilot was not injured; but the aircraft was damaged.




Synopsis: Observers reported to an Aeronca pilot that his aircraft's landing gear failed after takeoff. Upon returning to land on a grassy airport area; the right gear separated from the aircraft.
Date: 201705
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Sport / Recreational
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action

Narrative: After refueling I was taxiing for departure on runway 18. After viewing the windsock; I made a subsequent transmission on CTAF that I was changing to depart on runway 36. I held short of 36 while conducting a run-up; and then announced on CTAF that I was departing on runway 36. I conducted a scan of both directions of the runway for approaching traffic. Seeing no traffic; I entered runway 36 and commenced my takeoff roll. Just prior to rotation; a crop duster turned onto final for landing on runway 18. I heard no radio calls on CTAF from the aircraft. The aircraft maintained its course for far too long for my comfort. Immediately after rotation I veered right. The other aircraft conducted a go around; and landed on runway 36. I did not observe the tail number. My ADS-B receiver did not indicate the aircraft.I confirmed that the CTAF I had entered was correct. My radio was functioning correctly throughout my flight. I noted that the pilot lounge had a sign admonishing pilots to use the CTAF. The other aircraft did not respond to my subsequent radio calls. I can only assume that they did not use a radio. I did scan the approach for both runway 18 and runway 36. I did not scan the downwind legs for each pattern (left traffic for 18 was in the sun). I did not hear an aircraft in the vicinity prior to starting my engine. It is possible that a more thorough scan of the pattern may have located the other plane.




Synopsis: A general aviation pilot reported a near mid-air-collision during takeoff with an opposite direction landing crop duster that was not communicating on the CTAF.
Date: 202110
Local time of day: 1201-1800
Location: LIH.Airport, HI
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
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: Confusion; Situational Awareness; Troubleshooting
Anomaly: Ground Event / Encounter Other / Unknown; No Specific Anomaly Occurred Unwanted Situation
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Missing sign for Taxiway J (no yellow sign with black 'J') indicating approaching J while taxiing south on A.




Synopsis: Air Carrier Captain reported there is a missing taxiway sign at the intersection of taxiway A and J at LIH.
Date: 201710
Local time of day: 0601-1200
Location: ATL.Airport, GA
Flight conditions: VMC
Light: Dawn
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ATL
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Communication Breakdown
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Planned Runway 08R for takeoff per ATIS. Pre takeoff data for Runway 08R indicated flaps 5. Push back instructions by ramp control indicated a taxi to Runway 09L. During engine start (both) and after verifying final weights; I changed the runway in the FMC and sent for takeoff data for Runway 09L. Communicating with ground person on the push back was extremely distracting. Sounded like he did not put the microphone mask up to his face as background noise made him almost unreadable. I told him he needed a new headset. After giving disconnect headset; I said to set flaps 5; after start checklist. As we began to taxi; FO printed and accepted Runway 09L takeoff data and even said flaps 1. When we accomplished the before takeoff checklist; I think I said 1 final; 1 indicated green light; touching the flap lever; pointing to FMC takeoff page and comparing to flap indication. I may have said 5 final but somehow did not recognize the difference in the flap handle position versus the FMC takeoff page and flap indicator. During takeoff roll; flap 5 position was noted by the FO. Speed was about 80 knots. I considered it safer to continue versus reject. Takeoff with flaps 1 V speeds and subsequent flap retraction was uneventful. Bottom line is I miss compared the FMC takeoff page flap setting and the flap indicator along with a flap handle obviously in the wrong position. Not sure if the pushback crew headset distraction had anything to do with my subsequent mindset although it was the worst communication I've experienced between flight deck and push back person. Also not sure why FO did not advocate to reset flaps to 1 but ultimately it was me who missed the item during the before takeoff checklist.


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


Synopsis: B737 flight crew reported a takeoff with the wrong flap setting.
Date: 201812
Local time of day: 1801-2400
Location: ZZZ.Tower, US
Light: Dusk
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Flight phase: Taxi
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Landing Without Clearance; Ground Incursion Runway; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was working LCS2 and had multiple aircraft on frequency and was planning ahead for a few more that would be joining me. We were arriving and departing Runway 26L and 26R. I had departed a Helo from a ramp west bound and was getting ready to launch a Lear Jet. When I then noticed a low wing aircraft sitting at intersection A6 and was not passed the hold lines; so I couldn't depart. I couldn't see the call sign because he was pointed directly at me. I didn't know who it was. My ground controller didn't know who it was. I checked in on my Cherokee inbound from the North to be sure it wasn't him. He was still where I thought he was. Myself and the Ground controller reached out to the aircraft and didn't get any response. We then gave the aircraft a light gun signal. Still nothing from the aircraft. Then the pilot called me on frequency and said he was not at the right place. I told him to pull past the hold short lines and to contact ground control. The Aircraft landed opposite direction with no Mode C and without talking to ATC and didn't have a landing clearance.The sun was low and getting close to setting. So looking at Runway 8R in the scan doesn't help much because you are blinded by the sun.After review; the aircraft did not have Mode C on. When ground control asked the pilot for information; the ground controller told me the pilot thought he was at [another] airport and when he realized when he was on final for Runway 8R he just decided to land.I don't really have any thoughts on what I could have done better. I wouldn't and didn't see the aircraft because the sun was in a location that blinds you at that time of day. In addition; the aircraft didn't have mode C turned on with his transponder and made no contact with ATC.




Synopsis: Tower Controller reported seeing an aircraft at an intersection; not know what the call sign was or how it got there. The Aircraft had landed opposite direction without MODE-C on and was at the wrong airport.
Date: 201707
Local time of day: 0001-0600
Location: KOA.Airport, HI
Flight conditions: VMC
Aircraft: Helicopter
Operator: Military
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Initial Climb
Airspace: Class E HCF
ATC / advisory: TRACON HCF
Reporter organization: Government
Reporter function: Approach; Enroute; Handoff / Assist
Reporter qualification: Air Traffic Control Developmental
Human factors: Training / Qualification; Situational Awareness; Confusion
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Air Traffic Control Separated Traffic; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Airspace Structure; Procedure; Human Factors; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: Aircraft X requested one turn in holding at VECKI prior to one practice ILS 17 approach into KOA with the alternate missed approach followed by a clearance to [a different airport]. I was the D-Side so I coordinated the holding at VECKI; ILS 17; followed by the alternate missed approach climbing to 5;000. The holding and approach into KOA were accomplished with no issues. When Aircraft X checked back in with us on the missed approach he was observed making a right hand turn northbound. I notified the R-side and he asked Aircraft X what his intentions were. Aircraft X said he was on the alternate missed approach making a right hand turn to WERAK. WERAK is south of KOA at 174 degree radial 11.8 DME. While Aircraft X was northbound Aircraft Y was cleared for a visual approach Runway 17. Aircraft Z was cleared for a visual approach to follow Aircraft Y. The R-side proceeded to turn Aircraft X southwest bound away from the traffic and obstructions towards the ocean and safety below the Minimum IFR Altitude (MIA). Separation between aircraft was never lost. Aircraft X was clearly confused of what the alternate missed approach procedure entailed. Upon looking at the approach plate; the alternate missed approach is not depicted in the best manner and there is no written description to clarify the diagram.I would suggest the ILS 17 to KOA approach plate be revised to have a better description of the alternate missed approach procedure. In the diagram; there is nothing showing where the airport is and no written description of the procedure. This could be easily misinterpreted as shown in the event that was shown.




Synopsis: HCF TRACON trainee reported observing an aircraft deviate from the expected missed approach procedure below the minimum IFR altitude and towards arriving traffic.
Date: 201602
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Right after takeoff; received Smoke: Mid Cabin Master Warning indication.  Switched to Departure and informed of a smoke situation. Stopped climb at 2;000 feet; turned to north to set up for a landing.  We were given [another runway] as an option and decided to do that instead.  Ran minimum check list and landed.  Stopped straight ahead on the runway. Had Crash; Fire; and Rescue (CFR) do a thermal check. After getting the all clear; taxied to gate.


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


Synopsis: An A300 flight crew reported returning to departure airport after receiving a Master Warning for Smoke.
Date: 201201
Local time of day: 1801-2400
Location: VGT.Airport, NV
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: PA-42 Cheyenne IIA
Operator: Air Taxi
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Initial Climb
Airspace: Class E LAS
ATC / advisory: TRACON L30
Reporter organization: Air Taxi
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Communication Breakdown; Time Pressure
Anomaly: ATC Issue All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Airspace Structure; Environment - Non Weather Related; Human Factors
Primary problem: Ambiguous

Narrative: While starting engines about three minutes prior to Class D Control Tower closure; I asked North Las Vegas Tower/Control to provide my IFR clearance for a flight plan that was previously filed. They informed me that the Tower was closing and that my clearance would be void prior to departure (since the Tower was closing). The Ground/Tower Controller instructed me to contact Las Vegas Departure Control. I stated that I would depart VFR and contact Departure Control while airborne to pick up my IFR. After departure I made multiple attempts to contact Control on the frequency provided with no response. I continued on - stepping up beneath the Class B airspace to 7;500 FT MSL - approximately 17-20 NM from Las Vegas VOR. It wasn't until this time when Departure Control finally responded. At this position and course I was headed directly toward R-4806W. It was night; and there were mountains to the north (my desired direction); which at this altitude I was uncertain whether or not I could out-climb. It was imperative to have received a more prompt response from Departure Control to have received a timelier Class B clearance or IFR clearance. This clearance would have enabled me to initiate a climb much sooner; and would have removed my reluctance to make a turn toward the mountains.




Synopsis: A PA42 pilot; departing VGT; wass denied an IFR clearance by the Tower due to scheduled closure in three minutes. Reporter departed VFR and was unsuccessful in contacting Departure Control initially; resulting in difficulties avoiding Class B airspace and mountainous terrain to the north.
Date: 201503
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Robinson R22
Operator: Corporate
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Throttle/Power Lever
Component problem: Improperly Operated
Reporter organization: Corporate
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; General Flight Cancelled / Delayed
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: Training on infield of airport. As student raised collective and applied forward cyclic he also rolled the throttle off. The aircraft had barely made approximately 30 FT AGL and Instructor was unable to recover throttle; but was able to right aircraft from the turn and maintain a level touchdown preventing a rollover. The landing skids were spread on the aircraft as designed to cushion the landing. Instructor was in contact with ATC and advised that other than landing gear all was OK. Instructor checked over aircraft; flight checked at hover and requested permission to return to hangar. Student pilot was [elderly] and this was the first flight with this Instructor. Student had repeatedly rolled the throttle off in the previous hour during hovering maneuvers. Additionally; student was wearing a rubberized glove on his left hand that he indicated he needed to help his grip. Reporter believes this may have been a factor in ability [of the Instructor] to override. The Instructor had taken into consideration the student's 2000+ hours of flight time and [many] hours of recent rotorcraft instruction to give the student benefit that he knew his limitations; which he seemed to indicate if he needed assistance. Instructions had to be repeated numerous times. Age and ability seemed to be factors; but actual flight ability seemed to be within the limits of flight with an Instructor.




Synopsis: R22 student pilot inadvertently closed the throttle when raising the collective for takeoff. Instructor pilot took control and leveled the aircraft; but was unable to restore throttle. A hard landing resulted.
Date: 202008
Local time of day: 1201-1800
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: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: We were preparing the cockpit for departure and were given a form for the Refueling Door Cycling Procedure. I remember reading about this and I remember that a message must be sent. I also remember there was some verbiage that needed to be written in the text field.I could not remember exactly what needed to be written.  I found the reference and read through it quickly and I missed the area that had the required verbiage. Being close to departure time and not able to locate the exact verbiage I entered the Fuel on Board figure.  As a suggestion move the verbiage into a message. Also it would be very helpful if the reminder about the entry could include the verbiage on the form given to the cockpit crew from the fueler. The procedure and information that we need is readily available on this form.This was my first trip back flying in over 5 months and I was not as comfortable as I normally would be if I was flying a regular basis.  I will make sure that this does not happen again in the future.




Synopsis: Air carrier Captain reported not entering required verbiage onto a form and said that lack of recent flying contributed to the oversight.