Jump to content
View in the app

A better way to browse. Learn more.

Baseops Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

right thread this time....

I am sure those of you "in the know" have better knowledge...but the Air Force fish wrap has an article out...

https://www.airforcet...report-011112w/

Thoughts A-10 dudes?

Sounds like "core lock" on the motors. Same thing happened to a Pinnicle flight a few years ago that crashed in MO. Same engines I believe?

Sledy

  • 3 weeks later...
  • Replies 106
  • Views 40.7k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Not if they're not from this country, at which point they are considered a non-American-Asian! But if they are from the US, then they're called AAFES employees!

  • Well, I heard that two old men, Rainman and CH were in a wheel chair race, winner gets BQzip01's mom for the night. Dude saw the race and wanted to win, being in an A-10 he knew he had to eject and ra

  • Rainman won, I was worn out from nailing your mom.

right thread this time....

I am sure those of you "in the know" have better knowledge...but the Air Force fish wrap has an article out...

https://www.airforcet...report-011112w/

Thoughts A-10 dudes?

IIRC, the checklist called for a climb to 35K and involved a 1G stall/cabin pressurization check. Easily accomplished by slowly pulling the throttles to idle. Throttle or stick techique, i.e. ham fisting, the jet might have resulted in the problem. The jet has cables for both fuel control and flight controls and, if it wasn't rigged correctly, that may have caused the problem. However, prior to the 35K check, he would have shut down each engine (not at the same time) and done a restart via cross-bleed and APU at 15K. So, I'd say there is more to the story that we don't have via that link.

Can't blame the engines for the Pinnacle flight...

https://www.popularme...crashes/2156137

That article is crap...

"pitch up" maneuver that pinned them in their seats with 1.8 g's of force

HKKKKKK...... HKKKKKK..... HKKKKKKK....

the crew set the autopilot to climb at 500 ft. per minute--more than twice the fastest recommended rate

What is the recommended rate? Half of what is required without having to notify ATC?

The procedure requires at least 300 knots of airspeed. But at 20,000 ft. and only 236 knots...

7,000 ft to gain 67 kts.... Maybe gaining that much speed is harder in a larger aircraft?

The Bombardier has a 41,000-ft. service ceiling. However, according to the climb profiles in the crew's flight manual, the maximum altitude for the 500-ft.-per-minute climb the pilots set was only 38,700 ft.

So the service ceiling is 38,700 ft then?

So the service ceiling is 38,700 ft then?

"The service ceiling is the altitude at which the aircraft is unable to climb at a rate greater than 100 feet per minute (fpm)." FAA Pilot's Handbook of Aviation Knowledge page 10-7.

"The service ceiling is the altitude at which the aircraft is unable to climb at a rate greater than 100 feet per minute (fpm)." FAA Pilot's Handbook of Aviation Knowledge page 10-7.

500 fpm for jets... according to some definitions. Searching Google, it looks like all of the FAA definitions go with 100 fpm. Point conceeded, but the article is still rife with unnecessary hyperbole.

Yeah, my bad for the sub-quality article. I'd read something about it before (that was a lot better I think (AOPA?)) and guess I figured that's what would show up when I googled it. At second look there are a ton of narratives....

Regardless, it wasn't the engines.

Create an account or sign in to comment

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.