Saturday, September 10, 2016

Piper/CubCrafters PA-18-150 Super Cub, N906CC: Incident occurred September 10, 2016 at Fullerton Municipal Airport (KFUL), Orange County, California

FAA Flight Standards District Office: FAA Long Beach FSDO-05


Date: 10-SEP-16
Time: 21:05:00Z
Regis#: N906CC
Aircraft Make: PIPER
Aircraft Model: PA18
Event Type: Incident
Highest Injury: None
Damage: Minor
Flight Phase: LANDING (LDG)
State: California

FULLERTON ( — Authorities said the pilot of a light plane lost control at Fullerton Airport upon landing anr ran off the runway.

Neither the pilot or the passenger were injured.

The incident happened just before 2:10 p.m., according to the Fullerton Fire Department.

“The pilot of a Piper PA18, tail number N906CC, lost control after landing and ran off Runway 24,” FAA spokesperson Ian Gregor said. “Neither of the two people on board was injured.”

The FAA is investigating, he said.

Story and video:

FULLERTON – A small plane clipped a building and crashed on the runway as it landed at Fullerton Airport on Saturday afternoon.

No one was injured in the crash, according to Chief Kathy Schaefer with the Fullerton Fire Department.

As the single-engine plane hit the runway just after 2 p.m., Schaefer said its landing gear buckled beneath it. The Piper Cub Crafters reportedly clipped a building before skidding to a stop. There was a small fuel leak but no fire, Schaefer said.

Two people on board had managed to get off the plane before rescue crews arrived on the scene, Schaefer said.

Details on the cause of the crash weren’t yet available, as the investigation got underway.

There was another crash at Fullerton Airport, which is just northeast of the exchange of the 5 and 91 freeways, just a couple weeks ago.

On Aug. 24, a small plane owned by fantasy flight school Air Combat USA crashed into a hangar on takeoff, slightly injuring two men who were on board.

The 86-acre airport was founded in 1927 and is the last general aviation airfield left in Orange County.


Sen. James Inhofe tries to relax medical rules for private pilots • He wants to eliminate requirement that private pilots have medical release

Sen. James M. Inhofe (R-Okla.) takes a reporter on a flight above Tulsa in his experimental aircraft. 

WASHINGTON — Sen. Jim Inhofe of Oklahoma is trying to relax the medical requirements for private pilots who fly small planes, drawing complaints from Democrats who say is he is going back on a compromise that became law only two months ago.

The Oklahoma Republican, an avid, 81-year-old pilot who has had a quadruple heart bypass, is trying to eliminate a requirement that pilots have a statement from their doctor saying that they don’t have a medical condition that would interfere with their ability to safely operate a plane.

Inhofe, a member of the Senate Armed Services Committee, has proposed the change as part of House and Senate negotiations on a major defense bill, according to congressional aides familiar with the discussions. The aides spoke on condition they not be named because they weren’t authorized to speak publicly.

The defense bill already includes a “pilots’ bill of rights” sponsored by Inhofe — a series of provisions aimed at simplifying the medical approval process and helping pilots who contest enforcement actions by the Federal Aviation Administration.

But a compromise was reached earlier this year on the medical provisions, which were ultimately added to a bill extending the FAA’s policies and programs that was passed by Congress and signed into law in July.

The compromise means nearly 200,000 pilots who fly planes weighing less than 6,000 pounds and with up to six seats no longer must be certified every two years as medically fit to fly by an FAA-approved medical examiner.

Under the compromise system, which the FAA is still implementing, pilots can get a physical from any doctor — not just an FAA-approved medical examiner — and the doctor can simply attest that no prohibitive medical concerns were found.

The Aircraft Owners and Pilots Association and other groups whose members include recreational pilots had sought the changes, saying the previous system was overly bureaucratic and expensive, and discouraged pilots from flying.

The U.S. recreational flying industry has shrunk significantly. The number of general aviation pilots declined from 827,000 1984 to 593,000 in 2014. Industry officials say they are trying to encourage interest in flying.

But eliminating even the “moderate safety precaution” of having the doctor sign a statement that the pilot is fit to fly “would leave pilots with the exclusive responsibility for coming to a medical judgment about their own fitness to fly, which we believe would represent an unacceptable risk to the safety of our airspace,” Democratic Sens. Dianne Feinstein of California and Richard Blumenthal of Connecticut said in a letter this week to defense bill negotiators.

The letter urges them to reject the proposal. “Changes to civil aviation policy have no place in a military policy bill, recently negotiated compromises should not be re-litigated mere weeks after passage into law, and the safety of our airspace is too important to put at risk,” the senators wrote.

Donelle Harder, a spokeswoman for Inhofe, declined to comment on the specifics of the pilot medical changes the senator is seeking. “Things change by the hour, and Inhofe has a strong record of trying to find a middle ground that benefits all stakeholders,” she said.

Jim Coon, the pilots association’s top lobbyist, said his group isn’t aware of what proposals have been discussed but supports the medical provisions already in the law.


Beechcraft King Air 200, Hurricane Joaquin LLC, N369CD: Accident occurred September 10, 2016 at Orlando Apopka Airport (X04), Orange County, Florida

Aviation Accident Final Report - National Transportation Safety Board: 

Docket And Docket Items -   National Transportation Safety Board:

Aviation Accident Data Summary -  National Transportation Safety Board:


FAA Flight Standards District Office: FAA Orlando FSDO-15

NTSB Identification: GAA16CA475
14 CFR Part 91: General Aviation
Accident occurred Saturday, September 10, 2016 in Apopka, FL
Probable Cause Approval Date: 12/05/2016
Aircraft: BEECH 200, registration: N369CD
Injuries: 1 Uninjured.

NTSB investigators used data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator and did not travel in support of this investigation to prepare this aircraft accident report.

The pilot of a multi-engine turboprop airplane reported that during the landing flare he encountered a crosswind gust, which pushed the airplane to the right of the runway centerline. The pilot further reported that he applied power to abort the landing, but the airplane touched down in the grass to the right of the runway. After the wheels touched down in the grass, he reported that the power added "caught up with the aircraft," but the airplane was rolling toward trees and hangars. Subsequently, the pilot pulled the power to idle, but the right wing impacted a tree and the right main landing gear and nose wheel collapsed. A post-crash fire ensued after the collision and the right wing sustained substantial damage. 

The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

There was no record of the observed weather at the airport during the accident. An automated weather observing system about 14 nautical miles from the accident airport, near the time of the accident, recorded the wind variable at 5 knots.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:

The pilot's failure to maintain directional control during an attempted aborted landing in gusty crosswind conditions, which resulted in a runway excursion and an impact with a tree.

APOPKA, Fla. - A small plane caught fire after a minor crash Saturday at Orlando Apopka Airport, police said.

It happened around 4 p.m. at the airport at 1321 Apopka Airport Road.

Police said the pilot, identified as David Wishneski, was aiming to land on the runway but hit a tree after catching wind.

Fuel leaked and the plane caught fire. Police said the fire was quickly extinguished.

The pilot suffered a minor laceration to the head, but was not hospitalized.

Story and video:

APOPKA, Fla. —A pilot escaped serious injury when his plane hit a tree and caught fire while landing Saturday at the Orlando Apopka Airport.

The plane skidded off the runway while coming in for landing about 3:30 p.m.

The pilot, David Wishneski, escaped the crash with just a scratch to his head.

"I got caught by a gust of wind about ready to touch down and the wind picked up the left wing. I attempted to a go around and put power back in but by then it was too late," Wishneski said.

The plane's right wing came off and the engine caught on fire.

Wishneski was the only person on board.

The plane is a 1976 Beechcraft King Air 200. One expert said it's worth about $250,000.

The Federal Aviation Administration will investigate.

Story and video:

The pilot of a small plane suffered minor injuries after crashing into a tree while attempting to land at Orlando Apopka airport Saturday afternoon, police said.

David Wishneski, 71, was coming in for a landing about 3:30 p.m. but lifted back up when a gust of wind blew his Beechcraft King Air 200 plane from the runway and into a tree, said Apopka police Sgt. Ed Chittenden.

"He had basically landed but was going to make another pass at it and lifted back up when a strong gust got him," Chittenden said. "Pilots will do that often when they don't have enough space to land. They'll lift back off and do it again."

Aviation fuel leaked after the crash and caused a fire that scorched the grass and tree, Chittenden said. The incident caused a delay at the airport and planes were unable to land for several hours.

Photos of the plane show the right wing and engine was destroyed in the incident.

Wishneski was the only person on board during the crash and suffered a laceration to his head.

He refused to be taken to the hospital for treatment and is expected to be OK, Chittenden said.

Beechcraft A36 Bonanza, Central Penn Aviation Academy Inc., N36HT: Fatal accident occurred September 07, 2015 in Kernersville, North Carolina

Attorney Michael Apfelbaum, his wife Christy

Michael Apfelbaum, solicitor for the Shikellamy School District in Sunbury, Pennsylvania, is shown in this December 2014 file photo. Apfelbaum was killed in a plane crash south of Kernersville on September 7th, 2015.

Christine and Michael Apfelbaum 

FAA Flight Standards District Office:  FAA Greensboro FSDO-39

Docket And Docket Items:

NTSB Identification: ERA15FA340 
14 CFR Part 91: General Aviation
Accident occurred Monday, September 07, 2015 in Kernersville, NC
Probable Cause Approval Date: 08/31/2016
Aircraft: BEECH A36, registration: N36HT
Injuries: 3 Fatal.

NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.

The private pilot had recently purchased the airplane and it was more complex than the airplane he had flown previously. The accident airplane was also equipped with an upgraded avionics suite. The pilot had practiced loading and flying instrument approaches with the new avionics during recent flights with a flight instructor and another pilot onboard, and the flights were conducted in visual meteorological conditions (VMC). The pilot's most recent logbook was not available for review, so his instrument currency, as well as his recent and type of flight experience could not be verified. 

Review of the flight from departure to entry into the arrival airport's airspace revealed no unusual events or problems, and it was conducted in VMC. However, once the pilot began the higher workload phase of flight preparing to execute the instrument landing system (ILS) approach in actual instrument meteorological conditions, he began to exhibit some uncertainty and confusion. The first approach controller had to confirm the runway assignment three times and the pilot's assigned altitude once. After contacting a second approach controller, who vectored the flight to the ILS, the pilot had difficulty becoming established on the localizer, eventually causing the controller to cancel the approach clearance and issue vectors for a second attempt at the approach.

The instructions issued by the second approach controller were not complicated, but the pilot had difficulty flying assigned headings and altitudes. The controller also did not immediately detect some of the unusual maneuvers conducted by the pilot or recognize that he was perhaps suffering from spatial disorientation until the pilot explicitly said so. Instead of simply issuing a single heading and having the pilot climb a few hundred feet back into VMC, the controller asked the pilot if he was able to accept "no-gyro" vectors. The pilot accepted the offer, and the controller then issued turn instructions that required turns in both directions. This excessive maneuvering possibly exacerbated the pilot's spatial disorientation. The controller then directed the pilot to climb in an attempt to get him into VMC, but shortly thereafter, the airplane entered an aerodynamic stall/ spin and impacted terrain. When interviewed, the controller was unable to explain the basics of no-gyro vectoring and was unable to demonstrate the ability to effectively provide the service.

Facility management provided four summaries of training scenarios that included unusual or emergency situations, but none included no-gyro vectors or focused on identification of emergencies. Overall, the recognition of and response to emergencies did not appear to be a strong training item, which is not limited to this facility. The FAA training did not properly prepare the controllers involved in this accident to recognize and effectively respond to disorientation scenarios.

Examination of the airframe, engine, and flight instruments revealed no mechanical deficiencies that would have precluded normal operation at the time of impact.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The pilot's loss of airplane control due to spatial disorientation, which resulted in an aerodynamic stall/spin. Contributing to the accident was deficient Federal Aviation Administration air traffic control training on recognition and handling of emergencies, which led to incorrect controller actions that likely aggravated the pilot's spatial disorientation.

**This report was modified on August 31, 2016. Please see the docket for this accident to view the original report.**


On September 7, 2015, about 1203 eastern daylight time, N36HT, a Beech A36, was destroyed when it impacted terrain near Kernersville, North Carolina. The private pilot and the two passengers were fatally injured. The airplane was registered to Central Penn Aviation Academy Inc., Paxinos, Pennsylvania and operated by the pilot. An instrument flight rules (IFR) flight plan was filed for the flight that departed Sarasota-Bradenton International Airport (SRQ), Sarasota, Florida, about 0819, under the provisions of a 14 Code of Federal Regulations Part 91 personal flight. Instrument meteorological conditions (IMC) prevailed at the time of the accident.

According to radar and voice communication data provided by the Federal Aviation Administration (FAA), the airplane was being radar vectored by air traffic control for the ILS RWY 5R instrument approach to the Piedmont Triad International Airport (GSO), Greensboro, North Carolina, following a previous unsuccessful ILS approach to the same runway.

The pilot contacted GSO approach at 1132:54 and reported that he was descending through 5,700 ft. A controller replied that automated terminal information system (ATIS) information Delta was current, the altimeter setting was 30.19, and the pilot should expect to land on runway 5R. The pilot read back the runway assignment, and then asked if he should expect a visual approach. The controller stated that the pilot should expect the ILS approach, and asked the pilot to report when he had received information Delta. The pilot confirmed that he had information Delta, and then asked if the assigned runway was 5L. The controller reconfirmed the original assignment, runway 5R.

At 1133:51, the pilot asked the controller to confirm that he was cleared to descend to 5,000 ft. The controller responded that if 5,000 was the altitude assigned by the previous controller, it was correct, and also noted that he had not issued any other altitude instructions. The pilot acknowledged.

At 1135:14, the pilot again asked the controller to confirm whether he should expect runway 5R or 5L.The controller responded, "The right side – R I G H T." The pilot read back, "Five right 36HT."

At 1140:44, the controller instructed the pilot of N36HT to fly heading 360 for sequencing into GSO, and the pilot acknowledged. At 1143:26, the controller instructed the pilot to contact another controller on frequency 124.35.

The pilot contacted the controller at 1144:00 while the airplane was level at 5,000 ft. The controller provided the GSO altimeter setting, 30.19. At 1145:24, the controller cleared the pilot to descend to 3,000 ft. At 1148:01, the controller advised the pilot of potentially conflicting traffic ahead, type and altitude unknown. The pilot responded, "Roger – 36HT is about to go IMC." The airplane was descending through 3,600 ft at the time.
At 1148:38, the controller advised the pilot that traffic was no longer a factor and instructed him to turn right heading 010 degrees. The pilot correctly read back the heading. At 1149:04, the pilot reported level at 3,000 ft, and then asked if the controller wanted him to remain at 3,000 ft. The controller responded, "Affirmative."

At 1150:35, the controller transmitted, "N36HT niner miles from Pagan, turn right heading 020, maintain 3,000 until established on the localizer, cleared ILS runway 5R approach. The pilot responded, "Turning right heading 020 for Pagan." The controller restated the altitude restriction and the approach clearance, and the pilot correctly read it back.

At 1152:48, the pilot asked, "How do you like this route of flight?" The controller responded, "You look just a little bit right of course for the ILS, turn left heading 0…make that 360 for the ILS, report established." The pilot then asked, "Turning left or turning right for 360?" The controller replied, "left to 360," and the pilot acknowledged.

At 1153:59, the controller asked the pilot, "…are you established? [on the localizer]" The pilot responded, "Established if I could have vectors to final, please." The controller then asked, "…Are you established on the localizer?" The pilot stated, "I believe I am, 36HT." The controller continued, "Now you look like you just actually went through the localizer." The pilot replied, "Roger – request a vector for final for 36HT." The controller issued an instruction to another airplane, then at 1154:30 transmitted, "N36HT cancel your clearance, maintain 3,000, turn left heading 320 for sequencing." The pilot read back, "Left 320."

At 1156:42, the controller instructed the pilot to turn left heading 230 degrees for vectors to the ILS runway 5R approach. The pilot correctly read back the instruction.

At 1157:30, the controller asked the pilot to verify that he was flying heading 230. The pilot replied, "Negative, and 36HT is close to..." The transmission ended incomplete. The controller then took a coordination call from another facility. During that call, the pilot called again in a strained tone, stating, "N36HT request vectors," and the controller also noticed that the airplane's altitude was below 3,000 ft. He ended the call and at 1157:57 responded to the pilot, "Bonanza 36HT you need to be level at 3,000, altitude shows you 2,500, Greensboro altimeter 30.19." The pilot responded, "6HT climbing to three." The controller asked the pilot to verify that he was on a 230 heading. The pilot did not respond.

At 1158:40, the controller asked the pilot to verify the airplane was at 2,900 ft. The pilot did so. At 1159:16, the controller asked the pilot to verify the airplane's heading. The pilot responded that the airplane was heading 166. The pilot continued, "We need a descent, we are almost disoriented, N36HT…2,700." In the background of the transmission, a female voice said, "Turn something off."

At 1159:43, the controller instructed the pilot to start a left turn and 16 seconds later told him to maintain 2,500 ft. The pilot did not acknowledge the turn, but radar data indicated the pilot initiated a left turn. At 1200:16, the controller instructed the pilot to start a right turn. The pilot responded, "Right turn, 36HT leveling off 2,500." At 1200:47, the controller transmitted a low altitude alert to N36HT along with the altimeter setting, and asked the pilot to say altitude. The pilot did not acknowledge the transmission, and radar data showed that during the next minute the airplane initially turned right but then entered and completed a 360-degree left turn.

At 1201:25, the controller transmitted, "N36HT climb and maintain 4,000, I can see if I get you back up into the uh above the clouds." At 1201:35, the controller continued, "N36HT Greensboro approach you up? Last altitude showed 2,100." At 1201:41, the pilot transmitted "N36HT" in an agitated voice. The controller replied, "N36HT just climb and maintain 4,000, I'll block altitude for you."

At 1202:06, the controller asked the pilot of N36HT, "… if he was able to take the climb", and continued, "Last tops were reported at 3,500, if I can get you up to 4,000 maybe you can square it back off." At 1202:18 a short sound was heard, possibly from the pilot. At 1202:39, the controller advised the pilot that his altitude was 2,100 ft.

At 1202:44, an unidentified transmission of what sounded like breathing was heard on the frequency. At 1202:54, the pilot asked, "Is there a nearby field for 36 ho-." The controller responded, "…the nearest airport is Greensboro airport, off your left wing and off your current heading 7 miles. Right now showing 1000 overcast for the ceiling."

At 1203:21, the controller asked the pilot for his altitude. At 1203:34, screams were heard on the frequency. There were no further communications with the pilot.

Several witnesses observed the airplane just prior to the accident. One witness stated that when he first saw the airplane, it was "very low" in the sky and was in a "sharp left turn" toward the west. He said the airplane was banking so sharply that the wings appeared to be vertical to the ground. A second witness stated that the airplane was flying low and was beneath the "low clouds." She said the airplane, "...looked as if it were a trick plane practicing stunts or else someone trying to stabilize the plane but continuing to overcorrect as the nose would go down then up and the wings would go from right to left and back, but it never stabilized." She also said the airplane was going "very slow." She last saw the airplane descend behind a tree line and out of her view, but she could still hear its engine. She described the sound being similar to when a lawn mower engine "quits right before it runs out of gas." She said the engine revved up and then slowed, revved up and slowed, and then about 5 to 10 seconds later she heard a loud pop similar to a bottle rocket.

A third witness was in his front yard when he saw the airplane flying from right to left away from the airport. He said the airplane appeared to be flying normally and the engine was operating as if "everything was normal." A few minutes later the airplane turned back toward the airport. The witness said that before the airplane's wings leveled, the left wing dropped, followed by the right wing in a swaying motion. The witness said that as the right wing was coming back up to level, the airplane descended below the tree line and disappeared from view followed by the sound of an impact.

A fourth witness was in her front yard when she observed the airplane in a "severe" bank to the right heading toward the southeast. She said the airplane made a sharp right turn and "spiraled downward making 3 to 4 rotations" before it disappeared from view behind trees. Shortly after, the witness observed black smoke coming up from behind the trees where she last saw the airplane.


The pilot held a private pilot certificate with ratings for airplane single-engine land, and instrument airplane. His last FAA third-class medical was issued on April 17, 2014. At that time, he reported a total flight experience of 750 flight hours. The pilot's most recent logbook was not recovered and his overall flight experience and currency were not confirmed.

The pilot resided in Pennsylvania and had flown down to Florida on September 4, 2015, with his wife, father-in-law, and a friend, who was also a pilot and owned a Beech A36. According to the friend, the pilot had recently purchased the airplane and wanted to have another pilot along since this was his first long flight in the airplane. The friend estimated that the pilot only had about 6 hours of flight time in the airplane before the flight. The friend said the flight to Florida was uneventful; the airplane flew well, and the weather was mostly visual flight rules (VFR). The airplane was equipped with a Garmin 530/430 GPS, autopilot and a flight director, which were new to the pilot. During the flight, the friend helped the pilot practice loading instrument approaches into the Garmin 530 and they executed a practice instrument approach. The friend said the pilot had a lot of flight experience in instrument conditions in a Piper PA-28-180 airplane, but it did not have the advanced avionics or autopilot like the A36. The friend added that the pilot was getting more comfortable with the Garmin 530 and autopilot by the time they arrived in Florida.
The friend said the pilot dropped him off in Sarasota, Florida, and then the pilot and his family flew to St. Petersburg, Florida, to visit their daughter/granddaughter. The friend did not plan to return to Pennsylvania with the family the following Monday, but did monitor their trip via FlightAware. The friend was not aware if there was any reason the family had to get home on the day of the accident.

According to the pilot's primary flight instructor, the pilot had accrued over 800 hours of total flight time and had a lot of IFR experience in a Piper PA-28-180 airplane. The instructor said he had flown IFR with the pilot in the past and felt he was "very good and conscientious." After the pilot had purchased the accident airplane in August 2015, the instructor gave the pilot a complex check-out (6 hours flight time, 1.5 hours ground), which also included a demonstration on how to use the Garmin 530 for instrument approaches. These approaches were all done in VFR conditions and the pilot was not "under the hood." After the check-out, which was completed on September 2, 2015, 5 days before the accident, the instructor was not sure if the pilot flew the airplane before going to Florida; however, he did tell him not to fly in actual IFR conditions until he gained more flight experience.

The instructor said that the pilot had invited him and his wife to fly with them to Florida, but the instructor was unable to take the time off for vacation. So the pilot asked another friend to go. The instructor mentioned that the family was returning home on the 7th because the pilot's father-in-law was having surgery the following day. However, a family member confirmed that was not the case and it was just a standard doctor's appointment.


The six-seat, low-wing, single-engine airplane was equipped with a six-cylinder, horizontally opposed, fuel-injected, 285-horsepower Continental IO-520-BB engine (s/n 830171-R) that drove a three-bladed McCauley propeller (s/n EE3711B). The airplane's last annual inspection was conducted on March 6, 2015, at an airframe total time of 3,743 hours. The engine had accrued 326 hours since factory rebuild.


Weather reported at GSO, about 6 miles northeast of the accident site, at 1154, was wind from 090 degrees at 6 knots, visibility 10 statute miles, ceiling 1,100 overcast, temperature 23 degrees C, dewpoint 21 degrees C, and a barometric pressure setting of 30.19 in Hg.

According to Lockheed Martin, the pilot received two separate weather briefings through the automated flight service station (AFSS) system. The first telephone briefing was obtained before departing St. Petersburg and the other before departing Sarasota. The first briefing lasted about 3 minutes and 36 seconds. The pilot filed an IFR flight plan and reported the flight to Sarasota would take 15 minutes and he had 5 hours of fuel onboard. He requested a hazardous weather briefing and was informed that a convective SIGMET for embedded thunderstorms would be west along his route of flight. The pilot then interrupted the briefer and ended the briefing.

In Sarasota, the pilot again contacted AFSS and filed an IFR flight plan direct to GSO and asked for a hazardous weather briefing. The pilot said the flight would take 3 hrs and 30 minutes and he had 5 hours of fuel onboard. The briefer informed the pilot that an AIRMET for IFR weather was issued for northern and Central Florida, Georgia, South Carolina and North Carolina. The pilot then asked about the convective weather that was approaching Sarasota and was told that the leading edge of the storm was about 12.2 miles southwest of the Sarasota airport. The pilot then tried to end the briefing so he could leave before the storm, but the briefer said he had yet to provide the adverse weather information for the requested route of flight and would not be able to consider the briefing complete. The briefer also stated that he could get in trouble for not providing the weather that the pilot had requested from him, but would end the briefing if the pilot wanted to "cut him off." The pilot told the briefer to continue, but shortly after, interrupted him and said, "Ok, I am perfect. Thank you for all the help."


As part of the investigation, an NTSB air traffic control specialist conducted interviews of the controllers with GSO approach control, which included the controller who worked south-radar, west-radar, and their front line manager. The south-radar controller and the west-radar controller were both in contact with the pilot. The south-radar controller, who first handled the accident airplane as it approached GSO, said he did not think there was anything unusual about the flight, but felt it wasn't normal for the pilot to be so confused about which runway he had been assigned to land. He said it wasn't until after he had transferred the pilot to the west-radar controller that he noticed there was a problem when he saw the airplane was not properly lined up for the approach on runway 5R.

The west-radar controller said he was aware the pilot was disorientated and not maintaining headings and altitude. He said he was trying to get the accident airplane on a solid vector so the pilot could level the airplane and then later climb above the clouds to regain visual orientation. In an attempt to assist the pilot, the controller asked the pilot if he was able to accept no-gyro vectors, which is a procedure where a controller will tell the pilot when to "start turn" and "stop turn", with the expectation that the pilot will turn at standard rate, or 3 degrees per second. The pilot said he was able to accept the vectors. Though no-gyro vectors are commonly used by controllers when a pilot's gyroscopic heading indicator fails, the pilot never reported a malfunction.

In regard to no-gyro procedures, the west-radar controller said he was not familiar with standard rate turns and only knew to tell a pilot to stop the turn as he approached the desired heading. He could not recall the last time he received training on emergencies or how to determine an emergency situation. The controller said he could not recall receiving simulator training on emergencies at GSO and had no training since his initial controller certification. He described the situation involving the accident airplane as a "priority" but not an emergency. Facility management provided four summaries of training scenarios that included unusual or emergency situations, but none included no-gyro vectors or focused on identification of emergencies.

The front line manager was also aware that the accident pilot was disorientated and not responding to assigned headings or maintaining altitude. He said the west-radar controller was handling the situation well and he was helping him reduce workload so he could focus on the accident airplane. However, he did say that he "felt in his gut" that things were not going well and the situation was "serious." The front line manager heard the west-radar controller provide a no-gyro heading to the accident airplane and it appeared that the airplane was lining up with runway 5R, but it then disappeared off radar. When the target did not reacquire, the front line manager issued an "alert 3" for a possible accident. When asked about no-gyro procedures, the front line manager said he was familiar with standard rate turns and proper procedures for using them, but had not used them in many years. He said the best way to assist a pilot who is disoriented was to get them into visual conditions or get on the ground. It was important to get the airplane level, on a single frequency and to a safe altitude.

FAA Order JO 7110.65U, "Air Traffic Control"

Review of Section 10 of the order titled "Emergencies" provides controllers with the following guidance on recognizing and handling emergency situations:

Section 10-1-1 Emergency Determinations:

An emergency can be either a distress or an urgency condition as defined in the Pilot/Controller Glossary. The section also indicates that a pilot who encounters a distress condition should declare an emergency with the word "Mayday" preferably repeated three times, or "Pan-Pan" if an urgency condition also preferably repeated three times. If "Mayday" or "Pan-Pan" are not broadcast by the pilot but you (controller) are in doubt that a situation constitutes an emergency or potential emergency, handle it as though it were an emergency. Because of the infinite variety of possible emergency situations, specific procedures cannot be prescribed; however, when you believe an emergency exists or is imminent, select and pursue a course of action which appears to be most appropriate under the circumstances and which most nearly conforms to the instructions in this manual.


A postaccident examination of the airplane revealed it impacted terrain in an open area adjacent to an active rock quarry that had been recently graded and packed in preparation to start construction on a new building. The airplane came to rest upright about 6 miles southeast of GSO on a heading of 051 degrees. All major components of the airplane were accounted for at the accident site. A post-impact fire consumed a majority of the cockpit, fuselage, and both wings from the root to about mid-span. The tail section remained attached to the airplane and did not sustain any fire damage. Both wings remained attached to the airplane but sustained extensive fire and impact damage. Flight control continuity was established for all flight controls to the cockpit area. The flaps and landing gear were retracted.

Examination of the terrain around the main wreckage revealed the airplane had little to no forward movement when it contacted the ground, consistent with the airplane being in a steep nose down attitude at the time of impact. The airplane's windshield was fragmented and pieces of Plexiglas and parts of some of the flight instruments were found about 20-30 ft forward of where the main wreckage came to rest.

The engine remained partially attached to the fuselage and sustained extensive impact damage. The propeller flange and crankshaft were bent upwards and the top forward section of the engine crankcase was torn off exposing the internal components associated with No. 5 and No.6 cylinders. Since the crankshaft was bent, it could not be rotated.

The three-bladed propeller was buried, spinner side down, about 12-inches-deep into the ground. The spinner was crushed and the metal was peeled back. The propeller was separated and lying partially under the engine and main wreckage, which was lying flat on its belly. All three blades were loose in the hub but remained attached to the hub. Blade No. 1 was bent aft with some leading edge scoring; Blade No. 2 was bent aft and twisted with leading edge scoring with some gouging at the tip, and Blade No. 3 was bent aft with leading edge scoring.

The propeller governor, engine-driven fuel pump, throttle body/fuel metering unit, vacuum pump, alternator, starter motor/starter adapter, and oil pump were separated from the engine. The oil sump was fractured and the oil pick-up tube/screen remained attached to the fractured oil sump segment that remained with the oil pump. The pump was disassembled and no anomalies were noted to the pump gears or housing walls.
The engine-driven fuel pump sustained impact damage. The drive coupling was bent and could not be removed. The coupling could be rotated, but would bind on the areas where the coupling impinged the base of the pump. The pump was disassembled and no mechanical anomalies were noted.

The throttle body and metering unit sustained impact damage and had separated from one another. Examination of the throttle body revealed the valve was in the full-open position; however, it had sustained impact damage and the shaft was fractured. Witness marks consistent in size and shape as the edge of the throttle valve were noted on the inside walls of the throttle body. Positioning the throttle valve in the same areas as the witness marks placed the throttle valve in a near closed (or idle) position.

The manifold valve remained partially attached to the engine via the No.6 fuel injector line. The valve was disassembled and no anomalies were noted with the spring, plunger, and screen. The fuel injector nozzles were removed and each exhibited some form of deformation from impact. No anomalies were noted.

Both magnetos were separated from their respective mounting pads. The left magneto remained partially attached to the engine via the ignition leads. The housing was fractured, exposing some of the internal components. When the magneto was manually rotated the points opened and closed and the impulse coupling snapped. The right magneto sustained impact damage and all of the leads had separated. The unit was disassembled and the distributor and block were fragmented.

The spark plugs remained secure in their respective cylinders except for the top No. 1 plug, which was found in the wreckage. The No.1 spark plug's side-electrodes were stripped from the plug and found in the No. 1 cylinder. The other plugs were removed and each exhibit normal wear when compared to the Champion Spark Plug "Check A Plug" chart.

The internal chamber of the engine was examined with a lighted borescope. No mechanical deficiencies were noted that would have precluded normal operation of the engine prior to impact.

The vacuum pump was separated from the backside of the engine and sustained impact and thermal damage. The mounting flange was fractured and the two mounting studs that separated with the pump were sheared. The pump was disassembled and the rotor was fractured into four sections. All but one of the vanes remained intact except for one section that was fractured at the tip. The fractured tip was in a position that coincided with the narrowest portion of the pump's housing. The tips of each vane were smooth and there was no evidence of gouging on the pump wall.

The cockpit area sustained extensive impact and fire damage; however, the instrument air gauge needle and airspeed indicator were in relatively good condition. The instrument air gauge needle was stopped in the green arc, about 4.6 in Hg, and the air speed indicator needle was stopped about 189 knots. The altimeter sustained some impact damage. It indicated about 960 ft and 30.15 in Hg.

The horizontal situation indicator sustained extensive impact and thermal damage. The gimbal had separated from its housing and was found forward of the main wreckage. Examination of the internal housing revealed deep rotational scoring on the housing walls. Rotational gouging was also observed on the outer diameter of the gimbal.

The throttle, propeller control and mixture were all in the full forward position.


An autopsy was conducted on the pilot by the Wake Forest Baptist Medical Center, Department of Pathology, Winston-Salem, North Carolina, on September 9, 2015. The cause of death was determined to be multiple blunt force trauma injuries.

Toxicological testing was conducted by the FAA's Bioaeronautical Research Laboratory, Oklahoma City, Oklahoma. The results were negative for all items tested.


According to the FAA Flight Training Handbook, Advisory Circular (AC) 61-21A, page 9, "The flight attitude of an airplane is generally determined by reference to the natural horizon. When the natural horizon is obscured, attitude can sometimes be maintained by reference to the surface below. If neither horizon nor surface references exist, the airplane's attitude must be determined by artificial means - an attitude indicator or other flight instruments. Sight, supported by other senses such as the inner ear and muscle sense, is used to maintain spatial orientation.

However, during periods of low visibility, the supporting senses sometimes conflict with what is seen. When this happens, a pilot is particularly vulnerable to spatial disorientation. Spatial disorientation to a pilot means simply the inability to tell "which way is up."

According to an FAA Instrument Flying Handbook, AC 61-27C (Section II, "Instrument Flying: Coping with Illusions in Flight"), an illusion or false impression occurs when information provided by sensory organs is misinterpreted or inadequate and that many illusions in flight could be created by complex motions and certain visual scenes encountered under adverse weather conditions and at night. It also stated that some illusions may lead to spatial disorientation or the inability to determine accurately the attitude or motion of the aircraft in relation to the earth's surface.

The AC further stated that the most hazardous illusions that lead to spatial disorientation are created by information received from motion sensing systems, which are located in each inner ear. The AC also stated that the sensory organs in these systems detect angular acceleration in the pitch, yaw, and roll axes, and a sensory organ detects gravity and linear acceleration and that, in flight, the motion sensing system may be stimulated by motion of the aircraft alone or in combination with head and body movement. The AC listed some of the major illusions leading to spatial disorientation as follows:
"The leans - A banked attitude, to the left for example, may be entered too slowly to set in motion the fluid in the 'roll' semicircular tubes. An abrupt correction of this attitude can now set the fluid in motion and so create the illusion of a banked attitude to the right. The disoriented pilot may make the error of rolling the aircraft back into the original left-banked attitude or, if level flight is maintained, will feel compelled to lean to the left until this illusion subsides.

Coriolis illusion - An abrupt head movement made during a prolonged constant-rate turn may set the fluid in more than one semicircular tube in motion, creating the strong illusion of turning or accelerating, in an entirely different axis. The disoriented pilot may maneuver the aircraft into a dangerous attitude in an attempt to correct this illusory movement....

Inversion illusion - An abrupt change from climb to straight-and-level flight can excessively stimulate the sensory organs for gravity and linear acceleration, creating the illusion of tumbling backwards. The disoriented pilot may push the aircraft abruptly into a nose-low attitude, possibly intensifying this illusion.

Elevator illusion - An abrupt upward vertical acceleration, as can occur in a helicopter or an updraft, can shift vision downwards (visual scene moves upwards) through excessive stimulation of the sensory organs for gravity and linear acceleration, creating the illusion of being in a climb. The disoriented pilot may push the aircraft into a nose low attitude. An abrupt downward vertical acceleration, usually in a downdraft, has the opposite effect, with the disoriented pilot pulling the aircraft into a nose-up attitude...."
The AC also stated that these undesirable sensations cannot be completely prevented but that they can be ignored or sufficiently suppressed by pilots' developing an "absolute" reliance upon what the flight instruments are reporting about the attitude of their aircraft.

According to the FAA Instrument Flying Handbook, AC 61-27C (Section II, "Instrument Flying: Coping with Illusions in Flight"), an illusion or false impression occurs when information provided by sensory organs is misinterpreted or inadequate and that many illusions in flight could be created by complex motions and certain visual scenes encountered under adverse weather conditions and at night. It also stated that some illusions may lead to spatial disorientation or the inability to determine accurately the attitude or motion of the aircraft in relation to the earth's surface.

New flight plans at Baltimore Washington International Thurgood Marshall Airport (KBWI) bring jets lower, cause headaches for neighbors

Robyn and Jim Winder moved into their house on Skipton Drive in Hanover nearly a quarter-century ago.

The retired couple, both now 63, had hoped to stay there for the rest of their lives. But in the past year, the noise has become so unbearable that they have considered moving.

New flight patterns at BWI Thurgood Marshall Airport introduced by the Federal Aviation Administration in 2015, part of a nationwide air traffic update intended to save the airlines tens of billions of dollars. The FAA estimates that its $35 billion NextGen air traffic update will save $160 billion in fuel and other costs through 2030.

But NextGen has brought jets thundering lower over the Winders' neighborhood, day and night — exasperating neighbors for whom the airport had never been a problem.

Experience the original Swagger Wagon at the Toyota Annual Clearance Event. Save big on the only minivan that makes everyone inside feel like a real VIP, with space for up to eight.

"People say, 'That's what you get for living near an airport,'" Robyn Winder said. "We knew there was an airport, obviously. But we never noticed it, never heard the planes, never had a problem. It was just never an issue until NextGen. Now, it's nonstop hell."

Residents of Point Loma, Calif., near San Diego International Airport, have protested an adjustment that moved flight plans over their neighborhood. The city of Phoenix has sued the FAA over the noise caused by the new flight plans, which it said had "caused the community extreme discomfort with many unable to sleep at night or pursue normal daily activities."

BWI lies in northwestern Anne Arundel County, little more than a mile from the Howard County line. Neighbors in both counties have complained about the noise; airport officials say complaints have more than doubled since the flight paths changed.

Howard County officials met with FAA representatives in July to air their concerns. They planned a follow-up call for last week and a meeting on Monday, but the FAA has postponed them until October, at the earliest.

"We are continuing to work with [the Maryland Aviation Administration] and Howard County officials regarding residents' noise concerns," FAA spokeswoman Arlene Salac said. "We won't be providing anyone for an interview currently."

Upon hearing Salac's statement, Robyn Winder laughed out loud.

"Continuing to?" she asked. "That would be news, because they haven't."

Howard County Councilman Jon Weinstein, who organized the July meeting with the FAA, said it was productive. But he was surprised at how little the federal officials knew about residents' concerns.

County officials said the FAA initially blamed the noise on a runway renovation at BWI. But the noise continues to trouble residents long after that project wrapped up.

"Much to my disappointment, we're not much further along than just registering our complaints with them," Weinstein said. "I will say the 'working with' part is not apparent to us at this stage.

"Since we had that meeting in July, we have not had any substantive communication with them except for trying to schedule — and then canceling — a meeting."

Howard County Executive Allan H. Kittleman said, "It's safe to say we're frustrated."

The Howard County Council sent a letter to FAA Administrator Michael P. Huerta in May detailing its efforts for more than a year to get the agency to focus on the community's concerns.

"To date, our requests to your office for a resolution have not received an adequate response," the council wrote. "In fact, your most recent letter referenced the Potomac River, suggesting your office did not fully research this issue to understand our community concerns but rather may have copied content from another letter regarding issues associated with Reagan Washington-National Airport."

The Maryland Aviation Administration found that the NextGen flight plans violate both the airport's Noise Compatibility Program and the state's Noise Abatement Plan. It relayed both findings to the FAA in an October 2015 letter.

The FAA had said NextGen at BWI would involve no changes below 3,000 feet. The MAA's letter — and a slew of angry residents — contradicted that assertion.

"To describe NextGen as having no impact below 3,000 feet ... then to implement something entirely different, where planes fly directly over 1,500 new residential units at an elevation of less than 2,000 feet, is scandalous," Drew Roth, president of the Greater Elkridge Community Association, wrote in an online forum. "It is fraudulent. It is dishonest."

Noise complaints at BWI have more than doubled in the past two years, from 835 in 2014 to more than 1,800 last year.

Lynn Campbell has lived in Severn, a few miles from the airport, for some three decades. It was not until March 2015 that airplane noise began to affect her neighborhood's quality of life, she said.

Now, she said, "we've got the hot line for the noise complaints about BWI on speed dial."

"It actually shakes the house," Campbell said. "I have some plates hanging on the walls and they'll rattle."

Bob Stelmaszek, a former air traffic controller who worked at BWI in the 1970s, has lived in his home in Millersville for more than 30 years.

These days, he said, if he is outside and a plane flies overhead, "you have to stop your conversation. It gets pretty annoying after a while."

Kittleman said he is doing what he can to stop the noise. "Unfortunately, our hands are somewhat tied if we can't get the FAA to meet with us," he said.

Jeffrey Starin, an environmental activist based in New York, tracks news reports of noise complaints across the nation on his website, He says neighbors who are bothered by the noise might have only one option: move away.

"Moving could drive property values down, which would send an important message to city officials," he said. "However, most people don't have that option, and they could contact their elected officials to put pressure on Washington to pass comprehensive and substantive environmental reform legislation. ... This is not something that's going to be resolved relatively soon."

Because the FAA does not answer to local governments, Starin said, congressional action would be required to alter NextGen.

The NextGen updates are projected to save $9.4 billion in fuel costs, $30.2 billion in crew and maintenance costs, and $125 million in additional flights, according to the FAA's website. NextGen is also expected to reduce carbon dioxide emissions, save time and make flights safer.

Southwest Airlines, which operates about 70 percent of the flights into and out of BWI, did not respond to requests for comment for this article.

The planes' engines not only keep Sandy Cook, 48, and her family up all night in their home on Hanover Crossing Road in Hanover, the racket rattles the walls.

"You can touch the wall and feel the vibration," she said.

Trying to get to sleep between planes is futile, Cook said. Instead, she's drinking more caffeine to get through the workday and worrying about the health effects of not sleeping properly for more than a year.

"We're considering moving," Cook said. "The quality of life has been shattered."

She feels compelled to explain to skeptics that her family did not sign up for the noise just by living near the airport.

"When you move into this area, the MAA has noise maps and noise zones, and you don't move into those noise zones," Cook said. "You should feel OK buying outside the noise zones."

When Barbara Deckert and her husband were considering moving to Claire Drive, three miles from the airport, in 1984, they parked their car in front of the property and listened for planes overhead. At the time, Deckert says, there was no problem.

NextGen has ruined "the ordinary pleasure of sitting in your backyard and listening to the birds and the trees," Deckert said. "Instead, we've got aircraft flying over our head at 107 decibels."

Their attic is heavily insulated and the windows are triple-glazed. She says it makes no difference.

"The noise still is far worse than it used to be," she said. "This NextGen system ... has been a huge detriment to the quality of human life to us little ants on the ground."

Story and video:

Challenger II, N6162Y: Accident occurred September 10, 2016 at Bisbee Douglas International Airport (KDUG), Bisbee, Cochise County, Arizona 

FAA Flight Standards District Office: FAA Scottsdale FSDO-07

NTSB Identification: WPR16LA179
14 CFR Part 91: General Aviation
Accident occurred Saturday, September 10, 2016 in Bisbee, AZ
Aircraft: MCCLUSKEY CHALLENGER II, registration: N6162Y
Injuries: 1 Uninjured.

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.

On September 10, 2016, about 0900 mountain standard time, an amateur built McCluskey Challenger II, N6162Y, executed a forced landing following a complete loss of engine power. The pilot (sole occupant) was not injured and the airplane sustained substantial damage to the left wing. The airplane was registered to a private party and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed about the time of the accident, and no flight plan had been filed. The flight originated from the Bisbee Douglas International Airport (DUG), Bisbee, Arizona. 

The pilot reported that the purpose of the flight was to practice touch-and-go landings, and maneuvers. After the maneuvers, the pilot was climbing to traffic pattern altitude when the engine suddenly lost complete power with no indications or abnormal noises. The pilot executed a forced landing onto a field. During landing, the landing gear collapsed and the left wing impacted the ground. 

The airplane has been recovered to a secure location for further examination.

BISBEE, AZ (Tucson News Now) -    A 37-year-old Sierra Vista man was unharmed after crashing an aircraft he was testing at the Bisbee Airport Saturday morning, according to authorities.

The incident happened around 9 a.m., when the engine died out on the man's ultralight airplane while he was between 700 and 800 feet.

"I don't believe he fell straight down 700 feet. It was more likely a gliding situation," said Carol Capas, a Cochise County Sheriff's Office spokeswoman.

The man and his friend, who also was unhurt, were able to gather up their gear pretty quickly and leave, she said.


More air passengers jetting out of Provo, Ogden - Utah

Attracted by offers of cheaper fares and the convenience of less-crowded airports, a growing number of Wasatch Front residents are jetting out of Provo and Ogden.

The number of passengers in Provo has more than doubled since 2013, while Ogden saw a more modest 6.7 percent increase during the same period.

About 130,000 passengers passed through the Provo airport last year, according to the Federal Aviation Administration. That's about 169 times fewer than the 22 million who used Salt Lake City International Airport — helping to make for a more leisurely experience. About 30,000 used the Ogden airport, or 733 times fewer than Salt Lake City International's count.

The increases are "all about low fares and convenience," said Keith Hansen, vice president of airports and government relations for Allegiant Air, the only airline serving Ogden and Provo. It does not fly to Salt Lake City International.

"What we love about small airports, and Provo and Ogden fit right in, is that you land and you are two minutes, at most, away from your rental car. Or if you drove and parked, you're two minutes away. You don't have the big intimidating airport with a long walk and a train and everything else."

The smaller airports also often offer lower airfares. Allegiant's one-way base fares often start at $45 out of Provo and Ogden to Western destinations. However, that airline adds fees for any desired carry-on and checked baggage, snacks and reserved seating, which can more than double the base fare, depending on what's purchased.

Allegiant generally offers flights a few days per week out of those airports, when demand is highest, to avoid losing money on low-demand travel days. Because of that, it sells no connecting flights — only direct service to such places as Phoenix, Los Angeles, Oakland, Calif., and San Diego.

Still, "The planes are full" out of Provo and Ogden, Hansen said. "We feel very good about Provo and Ogden."

Las Vegas-based Allegiant, which serves 118 airports nationwide, uses a business plan that targets price-conscious leisure travelers instead of business passengers, and focuses on underserved or otherwise unserved airports.

"In the case of Provo and Ogden, those were both unserved airports at the time we started flying there," Hansen said.

In 2012, Allegiant started twice-a-week service between Ogden and Phoenix-Mesa Gateway Airport. It has not increased flight offerings since.

"We've certainly had discussions with the airport and the city about adding additional routes," Hansen said. "It's certainly possible it could grow, but for right now, we're at a good place."

Allegiant's service in Provo began in February 2013 (after Frontier Airlines ended a two-year experiment with flights from there to Denver), also with flights to Phoenix-Mesa. It has since added flights to Los Angeles and Oakland, and it will begin service to San Diego on Sept. 29.

Frequency also has increased on some of those routes, including seasonal six-days-a-week flights to Phoenix-Mesa.

Provo service may be growing more quickly because "you've got two big universities there — Utah Valley and Brigham Young universities." Hansen said. "I certainly think that helps."

But a bigger factor is "people not wanting to drive all the way up to Salt Lake," Hansen said. "In Provo and Ogden, you can fly right out of your backyard if you live in those communities."

The smaller airports also come with the advantage of cheaper parking. Economy lots at Salt Lake City International charge $9 a day, compared to $4.50 at Provo and $3.50 at Ogden.

Passengers are coming not just from Ogden and Provo, Hansen said, but many are driving from Salt Lake County. "People are going to drive for low fares."

Hilarie Grey, director of corporate communications for Allegiant, said her airline targets leisure travelers who are trying to save money to afford vacations. One way Allegiant keeps fares low, Hansen said, is by what it calls "the unbundled mile."

"That means that you pay for the items that you want on top of the base-fare ticket," he said. "So we don't include in the cost of the ticket any bags, any drinks, any snacks, seat assignments."

Hansen acknowledges that this practice brought criticism that some consumers feel nickel-and-dimed to death.

But, he said, "If you don't want to check a bag, you shouldn't have to check a bag. If you don't want pretzels, peanuts, chips and a Coke on a plane, you shouldn't have to pay for it. While others offer that for 'free,' what they are doing is figuring the cost of that into the ticket. So you pay for it whether you want it or not."

Allegiant's average one-way fare in the region is $75, Hansen said, compared to a $189 average in the industry. Once ancillary items most people want are added in, he said, Allegiant's average charge rises to $109, compared to an industry average of $196.

Baggage fees on Allegiant can be as expensive as the airfare itself. In Ogden and Provo, the airline charges $50 per bag ­— for carry-on or checked baggage — if the fee is paid at the airport. If paid at booking, the fee is $15 for a carry-on, and $20 for a checked bag.

Unlike most airlines, Allegiant does not sell connecting flights.

"The most important thing we can do is to keep our costs low so that our fares stay low," Hansen said. One way Allegiant does that is flying only when it believes a high demand exists — meaning it may offer some routes twice a week.

"Nobody begins or ends their vacation on a Tuesday," Hansen said. "So Thursday, Friday, Saturday, we tend to be pretty busy. Tuesdays and Wednesdays, we have a pretty light schedule."

By not flying when demand is low, Hansen said, "we're not having to charge so much on the peak days to offset what you're losing on the nonpeak days."

Because of complications from the low-frequency offerings, "We don't sell connecting flights." He said some people arrange connections on their own by studying schedules. "But that's not what we're trying to do. We're all about the nonstop flights from your home town to your favorite leisure destination."

Since 2013, Hansen said, 200,000 passengers have boarded Allegiant flights in Provo. Another 65,000 have flown out of Ogden.