Strict Standards: Redefining already defined constructor for class wpdb in /homepages/8/d29878190/htdocs/wp-includes/wp-db.php on line 57

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/8/d29878190/htdocs/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/8/d29878190/htdocs/wp-includes/cache.php on line 384

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/8/d29878190/htdocs/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/8/d29878190/htdocs/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /homepages/8/d29878190/htdocs/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /homepages/8/d29878190/htdocs/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/8/d29878190/htdocs/wp-includes/classes.php on line 560

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/8/d29878190/htdocs/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/8/d29878190/htdocs/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /homepages/8/d29878190/htdocs/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /homepages/8/d29878190/htdocs/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/8/d29878190/htdocs/wp-includes/classes.php on line 684

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/8/d29878190/htdocs/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/8/d29878190/htdocs/wp-includes/theme.php on line 540

Strict Standards: Redefining already defined constructor for class ngg_Tags in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/lib/nggallery.lib.php on line 481
elsishans.de
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 692

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 627

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 691

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-includes/kses.php on line 692


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

T-Rex 250, AC3X, Hyperion HS 2206, YGE 18


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26
20. Februar 2010

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-content/plugins/contact-form-7/wp-contact-form-7.php on line 71

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 203

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 267

Strict Standards: Non-static method nggallery::get_thumbcode() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 287

Strict Standards: Non-static method nggallery::create_navigation() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 310

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Ich habe in meinen T-Rex 250 endlich einen stärkeren Motor (Hyperion HS 2206 Kv 3900) und einen echten Drehzahlregler (YGE 18) eingebaut. Die Kombination hat deutlich mehr Leistung als die originale. Allerdings verkürzt sich die Flugzeit um 30 Sekunden auf 4 Minuten, wenn man die Mehrleistung auch nutzt. Der YGE arbeitet im “Governor store” Modus zuverlässig und hält die Drehzahl während des gesamten Fluges konstant.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

T-Rex 450 Pro mit Align 3G FL 760


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26
16. Februar 2010

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-content/plugins/contact-form-7/wp-contact-form-7.php on line 71

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 203

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 267

Strict Standards: Non-static method nggallery::get_thumbcode() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 287

Strict Standards: Non-static method nggallery::create_navigation() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 310

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Ich habe mir ein Align 3G Flybarless System gekauft.
Es kam heute morgen und wurde sofort in den Rex 450 pro eingebaut. Einbau und Einstellungen gehen recht schnell. Die Stecker halten allerdings fast garnicht im Empfänger. Diese musste ich zusätzlich sichern.

Ich habe bis jetzt 9 Füge damit gemacht. Erster Eindruck: steuert sehr direkt.
Also erstmal Expo auf die Taumelscheibe. Im Vorwärts- / Rückwärtsflug leichtes Pendeln über Nick. Gain auf 9 Uhr gestellt, Pendeln ist besser aber nicht ganz weg. Er macht irgendwie immer einen Wellenflug, wenn er etwas schneller wird.

Der Rex schwebt damit nach meiner Meinung nicht besser als mit Paddelkopf, aber bei Tictocs, Überschlägen etc. ist sämtliches Eigenleben verschwunden.

Danach testete ich Pirouetten auf der Stelle!  Es war nur leichter Wind, aber der Rex macht keine sauberen Piros. Kein Vergleich zu AC3X oder VStabi, bei denen der Heli dabei fast wie angenagelt auf der Stelle steht. Man merkt die fehlende Piro-Kompensation des 3G deutlich. Piroloops fallen mir unglaublich schwer und sind sehr gewöhnungsbedürftig. Ich empfinde diese Figur ist schwieriger  zu fliegen als vorher mit dem Paddelkopf! Sämtliche Pirofiguren mit Fahrt müssen ausgesteuert werden.
Danach habe ich den 250er Rex mit AC3X geflogen und wow, alles wie immer. Pirofiguren gingen leicht von der Hand. Kein Vergleich, kein Stress.

Mein erstes Fazit: Bei Pirouettenfiguren merkt man die fehlende Piro-Kompensation. Das können die deutschen Systeme besser. Auch fehlen die Einstellmöglichkeiten um den 450er auf der Nickachse besser zu stabilisieren. Entweder er wobbelt oder er stabilisiert nicht so gut. Bei größeren Helis fällt das wahrscheinlich nicht so sehr ins Gewicht, denn auch deutsche System hatten in früheren Versionen besonders mit kleineren Helis so ihre Schwierigkeiten.
Das ganze System erinnert im Flugverhalten eher an den zuvor geflogenen Paddelkopf, als an ein elektronisches Stabilisierungssystem. Allerdings hat der Paddelkopf eine “eingebaute” Piro-Kompensation, weshalb er meiner Meinung nach die Pirofiguren besser macht als das 3G!
Beim Einstellen fehlt mir eine Subtrimm Funktion, um die unterschiedlichen Servomitten auszugleichen. Die Servohebel stehen nämlich nie alle genau 90 Grad zum Servo. So muss man mühsam an den Gestängen herumstellen. Wenn man es über die Subtrimm Funktion des Senders macht, kann es nach ersten Berichten aus den amerikanischen Foren Probleme geben.

Update: Ich habe den Rex jetzt auf Hitec Digitalservos umgebaut, da diese im Rave 450 VStabi hervorragend arbeiten. Vielleicht gibt es dadurch eine Verbesserung im Flugverhalten.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Three Dee Rigid Haube


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26
22. Juli 2009

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-content/plugins/contact-form-7/wp-contact-form-7.php on line 71

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 203

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 267

Strict Standards: Non-static method nggallery::get_thumbcode() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 287

Strict Standards: Non-static method nggallery::create_navigation() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 310

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Heute ist die von mir in Auftrag gegebene Rigid Haube gekommen. Die Qualität ist absolut spitze.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

T-Rex 250 mit und ohne Stabistange


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26
24. Januar 2009

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-content/plugins/contact-form-7/wp-contact-form-7.php on line 71

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 203

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 267

Strict Standards: Non-static method nggallery::get_thumbcode() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 287

Strict Standards: Non-static method nggallery::create_navigation() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 310

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Nachdem der T-Rex 250 so gut flog und richtig Spaß machte, dachte ich mir: Das muss doch auch ohne Stabistange gehen. Leider fehlte mir noch die richtige Idee für den Umbau. Diese bekam ich dann von Christian Samuelis aus dem rc-heli Forum. Einfacher kann man das nicht machen! Der mechanische Umbau ist in 5 Minuten erledigt. Einfach die Stabistange mit Anlenkung entfernen und die Mischhebel am Rotorkopfzentralstück anschrauben. Dann noch eine kleine Kunststoffbuchse über die Hauptrotorwelle, damit der frei bewegliche Pitchkompensator nicht nach unten aus den Mitnehmerstiften herausrutschen kann. Fertig! Durch die indirekte Anlenkung muss man nicht einmal die Servowege begrenzen.

Beide 250er fliege ich mit dem 16er Ritzel und 100% Gasgerade.

T-Rex 250:

Alles serienmäßig bis auf Heckservo: Futaba 9257
SLS 860 22C  bzw. Kokam 910 15C Akku
Gewicht: 340g mit SLS, 352 mit Kokam
Blattschmied 195mm CfK Blätter

T-Rex 250 V-Stabi:

Align Motor
Hobby Wing 40A ESC (Gewicht: 34g; da muss ich noch abspecken)
Align DS410 auf TS
Hitec 5083 auf Heck
V-Stabi
SLS 860 22C bzw. Kokam 910 15C Akku
Gewicht: 371g mit SLS, 383g mit Kokam
Blattschmied 195mm CfK Blätter


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Next-D Rave 450 von Curtis Youngblood


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26
7. November 2008

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-content/plugins/contact-form-7/wp-contact-form-7.php on line 71

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 203

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 267

Strict Standards: Non-static method nggallery::get_thumbcode() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 287

Strict Standards: Non-static method nggallery::create_navigation() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 310

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 203

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 267

Strict Standards: Non-static method nggallery::get_thumbcode() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 287

Strict Standards: Non-static method nggallery::create_navigation() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 310

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Endlich gibt es auch einen Heli in der 450er Größe mit Starrantrieb. Motor (Scorpion 2221-6) und Rotorblätter (Radix 325) liegen dem Baukasten bei. Der Rave ist vom Aufbau und der Materialqualität beindruckend gut. Das Chassis besteht aus nur wenigen Teilen und ist sehr leicht. Insgesamt ist der Heli leichter als ein T-Rex 450 oder Outrage G5.
Das Heckrohr ist allerdings meiner Meinung nach für die Verwendung von 350mm Blätter etwas kurz geraten. Der Abstand Hauptrotorwelle zu Heckrotorwelle ist beim Outrage 1,5 cm mehr!


Die Kugelgelenke gingen am Anfang  sehr schwergängig.
Mit den Baukasten-Paddeln (zwei verschiedene) fliegt er sehr zahm. Ich habe dann die Stubz CfK Paddel ohne Gewichte montiert, damit dreht er sich wie verrückt und ist bei Vollausschlag kaum noch zu kontrollieren. Die beigelegten Gewichte sollte man unbedingt auf die Paddelstange montieren!

Ausgerüstet habe ich den Rave gleich mit dem 6s Setup des Outrage, da ich damit 6 Minuten 3D Flugzeit bei sehr guter Leistung habe. Mit dem mitgelieferten Scorpion 2221-6 kommt man nach meiner Erfahrung vom Rex nur auf 3,5 Minuten.

Ausrüstung:

Outrage 1700 kv Motor, 13er Ritzel
Jazz 40
Outrage 6s 1300 XP 25C
3 x 5065 Hitec Digital
1 x 9257 Futaba
Spartan ds760
Empfänger 617  2,4 GHz
Rotortech 350
Gewicht 890 g


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Neue Hauben


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26
18. Oktober 2008

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-content/plugins/contact-form-7/wp-contact-form-7.php on line 71

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 203

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 267

Strict Standards: Non-static method nggallery::get_thumbcode() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 287

Strict Standards: Non-static method nggallery::create_navigation() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 310

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Ich habe neue Hauben für den T-Rex 600 und T-Rex 700. Die 600er Haube ist von Canomod, die 700er von Fusuno.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Outrage G5


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26
1. Oktober 2008

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-content/plugins/contact-form-7/wp-contact-form-7.php on line 71

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 203

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 267

Strict Standards: Non-static method nggallery::get_thumbcode() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 287

Strict Standards: Non-static method nggallery::create_navigation() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 310

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Seit letztem Wochenende habe ich den Outrage G5.

Er ist ein Heli in der T-Rex 450 Größe, wird allerdings mit einem 6s Akku geflogen.

Am Wochenende habe ich ihn mit Paddelkopf eingeflogen. Er fliegt sehr gut, hat deutlich mehr Leistung als ein Rex 450 mit Align Motor und eine Flugzeit von fast 6 Minuten. Als Drehzahl hatte ich 2700/min  eingestellt, Rotorblätter waren die 325er Maniac.

Gestern habe ich den Outrage auf V-Stabi umgebaut. Der Outrage “Flybarless Head” ist sehr einfach aufgebaut. Er hat ein niedrigeres Zentralstück, als der normale Paddelkopf. Die beiliegenden Gestänge waren allerdings zu lang und mussten gekürzt werden. Das Unterbringen des V-Stabi in so einem kleinen Heli bereitete mir schon etwas Kopfzerbrechen. Durch V-Stabi wird der Heli etwas schwerer. Mein 450er T-Rex SE V2 mit Paddelkopf wiegt aber auch fast 900 g.

Momentan ist der  Outrage wie folgt ausgerüstet:

Outrage 1700 kv Motor, 11er Ritzel
Jazz 55-10-32
Outrage 6s 1300 XP 25C
V-Stabi
10 Ampere ccBEC von Castle Creations @ 6V
3 x 5065 Hitec Digital
1 x 9257 Futaba
Empfänger 617  2,4 GHz
Helitec 350
Gewicht 950 g


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

T-Rex 600 Nitro Super Pro


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26
20. Mai 2008

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-content/plugins/contact-form-7/wp-contact-form-7.php on line 71

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 203

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 267

Strict Standards: Non-static method nggallery::get_thumbcode() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 287

Strict Standards: Non-static method nggallery::create_navigation() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 310

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Strict Standards: Non-static method nggallery::get_thumbnail_folder() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 332

Strict Standards: Non-static method nggallery::get_thumbnail_prefix() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 333

Ich habe heute die ersten fünf Flüge mit dem Nitro gemacht. Obwohl der Motor noch nicht eingelaufen ist, geht der Nitro schon richtig gut.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

T-Rex 600 Nitro Super Pro


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26
19. Mai 2008

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-content/plugins/contact-form-7/wp-contact-form-7.php on line 71

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Ich habe heute den T-Rex 600 Nitro Super Pro fertig gestellt. Der Zusammenbau ging recht zügig, ohne größere Probleme. Nur der Tankverschluss hat mich etwas Nerven gekostet. Der Tank an sich ist etwas unglücklich gestaltet. Da liegt das Pendel gegen Ende der Flugzeit bei vielen Figuren nicht mehr im Sprit. Deshalb habe ich noch einen Headertank angebaut.

Die Ausstattung ist wirklich edel, allerdings sind das Lüfterrad und der Nickhebel immer noch aus Kunststoff.

Bilder werde ich morgen machen.


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26

Stratus mit V-Stabi


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/8/d29878190/htdocs/wp-includes/functions.php on line 26
25. April 2008

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/8/d29878190/htdocs/wp-content/plugins/contact-form-7/wp-contact-form-7.php on line 71

Strict Standards: Non-static method nggallery::get_option() should not be called statically in /homepages/8/d29878190/htdocs/wp-content/plugins/nextgen-gallery/nggfunctions.php on line 10

Ich habe meinen Stratus wieder!

Allerdings habe ich ihn mit V-Stabi ausgerüstet. Jetzt fliegt er so, wie ich es schon immer gern gehabt hätte. Näheres unter: Helis -> Stratus